pcdm:Collections, pcdm:Objects and pcdm:Files enforce behavior rules

[flyingzumwalt]

Note: If it's not possible to enforce these rules on Files for some reason, call it out on the scrum.

Object Behavior Rules

• Hydra::PCDM::Object can aggregate (pcdm:hasMember) Hydra::PCDM::Object
• Hydra::PCDM::Object can aggregate (ore:aggregates) Hydra::PCDM::Object (Object related to the Object)
• Hydra::PCDM::Object can contain (pcdm:hasFile) Hydra::PCDM::File
• Hydra::PCDM::Object can contain (pcdm:hasRelatedFile) Hydra::PCDM::File
• Hydra::PCDM::Object can NOT aggregate Hydra::PCDM::Collection
• Hydra::PCDM::Object can NOT aggregate non-PCDM object
• Hydra::PCDM::Object can have descriptive metadata
• Hydra::PCDM::Object can have access metadata

File Behavior Rules

• N/A - PCDM::File can NOT aggregate anything (no aggregation, so nothing to test)
• N/A - PCDM::File can NOT contain PCDM::File (no contains association defined, so nothing to test)
• PCDM::File can have technical metadata about one uploaded binary file

Collection Behavior Rules

• Hydra::PCDM::Collection can aggregate (pcdm:hasMember) Hydra::PCDM::Collection
• Hydra::PCDM::Collection can aggregate (pcdm:hasMember) Hydra::PCDM::Object
• Hydra::PCDM::Collection can aggregate (ore:aggregates) Hydra::PCDM::Object (Object related to the Collection)
• Hydra::PCDM::Collection can NOT aggregate non-PCDM object
• Hydra::PCDM::Collection can NOT contain Hydra::PCDM::File
• Hydra::PCDM::Collection can have descriptive metadata
• Hydra::PCDM::Collection can have access metadata

[elrayle]

Notes:

• Most of these are now covered by PR add tests for better coverage of pcdm objects #79 and previous commits that added tests.
• Object hasRelatedFiles Object is covered by PR Add related_files to Object. Fixes #62 #66
• See PR Implements Technical Metadata.  #70 for a discussion on technical metadata.

Outstanding Questions:

• Descriptive metadata is handled via properties set on subclasses. Should this be tested at pcdm level?
• Access metadata is TBD

[elrayle]

Questions related to descriptive and access metadata:

• How to distinguish between descriptive and access metadata?
• Are there any default properties to set for Collection's descriptive metadata?
• Are there any default properties to set for Collection's access metadata?
• Is there a way to override default properties defined in this class?

[elrayle]

Per scrum call...

• descriptive metadata is tested at the active-fedora level for properties and can be tested at a level beyond Hydra:Works where properties are defined
• access metadata will be tested under a separate ticket

Remaining unchecked items will be tested separately. See notes in previous comment.

Closing this issue.