Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

schema slot updates #587

Open
52 of 99 tasks
mslarae13 opened this issue Jan 6, 2023 · 6 comments
Open
52 of 99 tasks

schema slot updates #587

mslarae13 opened this issue Jan 6, 2023 · 6 comments
Labels
identifiers Tickets associated with identifier updates or needs nmdc-schema-mixs-submission

Comments

@mslarae13
Copy link
Contributor

mslarae13 commented Jan 6, 2023

Collecting all schema slot update issues here for tracking & to determine priority / squad work.
(Addition of tickets is still in progress)

Slot updates

New slots

DH/Submission portal

Schema Sheets

Other

@mslarae13
Copy link
Contributor Author

#581
Difficult to accomplish. LinkML only allows for 1 identifier column, and that's the source_mat_id column and also must be unique.
LinkML has unique keys to use, but they aren't checked.
Longer lived issue, backlog.

@mslarae13 mslarae13 changed the title schema slot updates schema slot updates (In Progress) Jan 6, 2023
@mslarae13
Copy link
Contributor Author

mslarae13 commented Jan 18, 2023

The following should be completed by NMDC SubPort squad

Slot updates

New slots

DH/Submission portal

Schema Sheets

Other

@mslarae13 mslarae13 changed the title schema slot updates (In Progress) schema slot updates Jan 18, 2023
@turbomam
Copy link
Member

de-assinging slot rel_to_oxygen form class Biosample. Will need to remove from sheets_and_friend workflow. There will probably be additional similar changes to reconcile.

@turbomam
Copy link
Member

bump

@mslarae13
Copy link
Contributor Author

@turbomam are you bumping because you'd like to see this prioritized?

@turbomam
Copy link
Member

turbomam commented Oct 6, 2023

Yeah, sorry about that. No I don't think it needs different prioritization. I just did that selfishly because it makes this appear higher in the list when I sort by "recently up[dated"

I guess a better solution would be for me to make a project of issues I don't want to forget about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
identifiers Tickets associated with identifier updates or needs nmdc-schema-mixs-submission
Projects
None yet
Development

No branches or pull requests

2 participants