-
Notifications
You must be signed in to change notification settings - Fork 5
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
berkeley
: Update minter to use first typecode when pattern contains multiple typecodes
#592
Labels
berkeley-schema
Related to making the Runtime work with the Berkeley schema
bug
Something isn't working
X SMALL
Less than 1 day
Comments
Closed
2 tasks
berkeley
: Adjust minting when id has multiple typecodes (like "(dgms|omprc)") to mint IDs with the first typecode
berkeley
: Adjust minting when id has multiple typecodes (like "(dgms|omprc)") to mint IDs with the first typecodeberkeley
: Adjust minting when id has multiple typecodes to mint IDs with the first typecode
berkeley
: Adjust minting when id has multiple typecodes to mint IDs with the first typecodeberkeley
: Update minter to use first typecode when pattern contains multiple typecodes
38 tasks
8 tasks
8 tasks
This is done in the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
berkeley-schema
Related to making the Runtime work with the Berkeley schema
bug
Something isn't working
X SMALL
Less than 1 day
In berkeley-schema-fy24, some of the syntax declarations on ids of classes result in extra parentheses during minting on the berkeley-schema nmdc runtime. This results in badly minted ids for instances of new classes.
There are two existing classes in the berkeley schema where the id typecodes need to be either "dgns" or "omprc", but the minter should only mint IDs for "dgns".
This class
Needs to mint ids with dgns (not omprc).
Criteria for Completion
minting for
NucleotideSequencing
andMassSpectrometry
classes generates ids with typecodes "dgns" and "dgms" respectively.Reference: microbiomedata/nmdc-schema#2122
The text was updated successfully, but these errors were encountered: