SOW: HYRAX - Completion of AllinsonFlex

[jillpe]

SoftServ will complete AllinsonFlex (https://github.com/samvera-labs/allinson_flex) work that includes
the development of a UI for administering flexible metadata in the admin dashboard. This work will
include the following steps:

1. Create a DatabaseSchemaLoader that mimics the SimpleSchemaLoader but is called on object
   instantiation
2. Add versions to database schemas and track schema versions in work types
3. Add interface to admin area to download and upload schema
4. Port existing AllinsonFlex work versioning UI over to new code
5. Expand DatabaseSchemaLoader to handle M3 (Machine-readable Metadata Modeling) spec
6. Port AllinsonFlex react UI for existing schemas
   In response to feedback from Hyku community users, this work will include:
   ● A UI for editing and creating metadata
   ● Optional ability to make updates with upload of Yaml file will be retained
   ● Ability to create and update new work types and metadata profiles
   ● Ability to create fields or edit/update field names
   ● Ability to determine which fields are required
   ● Contexts, a preset of metadata fields related to a specific repository or source, attached to an
   admin set, as implemented by Indiana University
   ● M3 (Machine-readable Metadata Modeling) metadata specification

Acceptance Criteria

• A UI for editing and creating metadata is available
• Optional ability to make updates with upload of Yaml file will be retained
• Ability to create and update new work types and metadata profiles
• Ability to create fields or edit/update field names
• Ability to determine which fields are required
• Contexts, a preset of metadata fields related to a specific repository or source, attached to an admin set, as implemented by Indiana University
• M3 (Machine-readable Metadata Modeling) metadata specification

Testing Instructions

1. Initital
   Visit the metadata profiles tab. v1.0 matches the basic schema defined by Hyrax/Hyku.
   Manually create a single work from the UI (from profile v1.0)

2. Customizations
   Visit the metadata profiles tab again. Download this profile as a start, and add custom properties.
   Upload the custom profile
   Create a new work (from profile v2.0)
   The form should render the additional properties, as defined in the uploaded profile.
   After saving, properties should render on the show page (if defined to do so)
   Note: We are aware there's a bug when removing properties

• 🐛 Removing properties from m3_profile causes errors #54

3. EDITING previously created works
   If you Edit a work that was created on a previous profile, its form will no longer reflect the metadata of the profile it was created on. The form and show page should reflect the metadata defined on the latest uploaded profile. If you save the work, it will be saved using the schema of the latest uploaded profile.
   The user will see this noted in the form via the profile badges, like

TASKS

• ☄️ 🎁 Create and expand Dynamic Schema functionality #5

  • 🎁 All the metadata in config/metadata/*_metadata.yaml needs to be translated to the m3 profile #15
  • 🎁 A copy of the m3 profile needs to be created in Dassie and Koppie that use the work types in Dassie and Koppie #16
  • 🎁 Loading the default profile should be added to the seeds if the flag is turned on for now (since an uploading interface is down the road) #17
  • ✅ Specs for SchemaLoader need to be done #18
  • ✅ Specs for Hyrax::FlexibleSchema need to be done #19
  • ✅ Spec coverage for Hyrax::Resource with dynamic loading need to be written #20

• 🎁 Select Admin Set while selecting work type #14

• 🦄 Understand AFlex versioning #8

• 🎁 Implement UI to upload yamls #9

• 🎁 Indexing Object Dynamic Loading #21

• 🎁 Form Object Dynamic Loading #22

• 🎁 Add a UI Display of which version an item is currently and what it will become after save #23

• 🦄 SPIKE: Add support from AFlex to Hyrax for rendering the attribute_rows dynamically #10

• ☄️ Epic: Add support from AFlex to Hyrax for dynamic views, for m3 profiles #11

• 🎁 Amigos: Integrate Hyrax dynamic metadata feature into Hyku #36

BUGS

• ☄️🐛 Epic: Allinson Flex Bug Tracking #39

Nice to Haves

• 🎁 Add faceting support to Hyrax through FlexibleSchema #26
• 🎁 Contexts needs to be implemented #24
• 🎁 Add support for Admin Only #27
• 🎁 Separate Profile Viewer && Editor into its own gem #12
• 🎁 Add Delete Action to m3 profile index page? #28
• 🎁 m3 validator? #29
• 🦄 SPIKE: Support Flexible Metadata per model #44
• 🎁 Add File Set UI support for Flexible Metadata #45
• 🦄 Does Bulkrax need to change for flexible metadata support? #46
• Extend dynamic views to collections #33
• Extend dynamic views to file_sets #34
• 🎁 Add Dynamic Metadata support for FileSet Edit #37

[ShanaLMoore]

client review is blocked by #54