Use case overview
- Priority: [High/Medium/Low]
- Status: [Draft/Under Review/Approved/Implemented]
Describe use case
A clear and concise description of a use case supported by BIG outputs (DCTAP and/or SHACL).
E.g. As a cataloger using a BIBFRAME editor, I would like the editor to check that my description validates using the BIG shapes without any errors
Preconditions (Optional)
List conditions that must be true before this use case can begin.
Describe expected behavior in related systems
A clear and concise description of related system behavior
E.g. Using the BIG SHACL, the editor would compare the description provided by the cataloger against the applicable BIG SHACL before saving the data. If the description does not confirm to BIG shape definitions, the cataloger would not be allowed to save the description and would be notified which fields in the editors are missing or require changes
Post conditions (Optional)
Success post conditions
What should be true after successful completion?
Failure post conditions
What should be true if the use case fails?
Main success scenario
What steps or conditions would this use case be considered to be a success?
Additional context
Add any other context or screenshots about the features you are requesting.
E.g. Using SHACL for validation in BIBFRAME editors like Sinopia and Marva has overlap with template creation in those systems
Use case overview
Describe use case
A clear and concise description of a use case supported by BIG outputs (DCTAP and/or SHACL).
E.g. As a cataloger using a BIBFRAME editor, I would like the editor to check that my description validates using the BIG shapes without any errors
Preconditions (Optional)
List conditions that must be true before this use case can begin.
Describe expected behavior in related systems
A clear and concise description of related system behavior
E.g. Using the BIG SHACL, the editor would compare the description provided by the cataloger against the applicable BIG SHACL before saving the data. If the description does not confirm to BIG shape definitions, the cataloger would not be allowed to save the description and would be notified which fields in the editors are missing or require changes
Post conditions (Optional)
Success post conditions
What should be true after successful completion?
Failure post conditions
What should be true if the use case fails?
Main success scenario
What steps or conditions would this use case be considered to be a success?
Additional context
Add any other context or screenshots about the features you are requesting.
E.g. Using SHACL for validation in BIBFRAME editors like Sinopia and Marva has overlap with template creation in those systems