Closed ShanaLMoore closed 6 days ago
To verify the metadata, I found the attributes for each existing work & collection model on the prod server:
types = ["GenericWork", "Image", "Collection", "Thesis", "ConferenceItem", "Dataset", "ExamPaper", "JournalArticle", "PublishedWork"]
Attributes are found via types each do { |type| type.constantize.new.attributes.keys.map(&:to_s) }
I then did the same locally for the new resource models.
Resulting differences are mostly as expected due to new features coming in via Hyrax/Hyku (pdf viewer options) as well as upcoming development (i.e. slugs).
Summary
Dog biscuits is replaced by the simple schema way for valkyrie objects.
SPIKE: https://docs.google.com/document/d/1iSlzEfM0ImPQXM2u-if3icuet52SaqHupNEPErTG-Go/edit?usp=sharing
Models
Steps
Identify all of the terms for each work type. Figure out which ones are not in the basic and core metadata yaml files. The yamls will get created when we run the generator to create the resources. We'll update these yamls with our findings.
Acceptance Criteria
Testing Instructions
Notes
To clarify, we are NOT removing dog biscuits entirely. However, new valkyrie models SHOULD NOT be using dog biscuits.
⚠ We CANNOT remove dog biscuits until the application has been fully migrated. ⚠