Page Comparison

...

• Description Tab
  
  • What metadata to include?
    • There are a number of fields for collections that most likely are a carry over from Sufia.  Don't know which ones are in actual use.  Seems beyond this working group to make that determination.  Perhaps the metadata working group has done some work on this.  For our development process, we will just put them under the Additional Fields button.  This will allow for future changes.
    • One concrete use case for extra metadata:  Cornell has an implementation where each collection represents an agency.  Each agency has contact information.  The contact information is stored as metadata for the collection.
    • Implementation Note: Some sites want to add additional fields that are specific to their application.  A way to define those and have them be part of the additional metadata would also be desirable.  I'm guessing that the Hydra::Works::Collections have a process for defining additional fields on collections that we can hook into.
  • Banner and logos
    • Can we add the ability to add alt-text for uploaded images?  This is a requirement for accessibility. (Note this probably only applies to the logos. I'd consider the banner image "decorative" and thus it should have an empty alt-text so screenreaders don't read it – Gary)
    • Can we add links for uploaded images?  This is probably not hard, but also not a top priority since it can easily be added later.
  • Description
    • Some concern about checking the rich-text editor to be sure it is accessible.
    • NOTE: This is the same editor used elsewhere in Hyrax.  Beyond the scope of this group to evaluate the accessibility.  But we can send it to the uxinterestgroup to evaluate it if they haven't already.
• Sharing Tab
  • The roles are Editors and Viewers.  Is there any reason not to make this the same as the ones for Admin Sets, i.e., Managers, Depositors, and Viewers, with the same abilities?  Gary didn't seem to think there was any reason not too and there was reason to use the same roles for consistency.
• Visibility
  • Adjust the wording to make it clear that this effects the visibility of the collection in discovery and access to show pages only.  It does not effect the items in the collection.
  • Should there be an APO that can serve as a template for newly created works that are created directly in the collection?
• Items
  • Adding an existing work to the collection VS. Creating a new work in the collection
    • Adding - go to the dashboard list of works and allow user to add to the collection
    • Creating - go to New Work and auto populate the collection field in the Relationships tab making the field readonly.  Return to the Items tab one work is created.
  • Questions:
    • Should adding/creating items be disabled while creating a new collection and only be available after the collection is created?  Otherwise, leaving the new collection workflow could result in the user not completing the process.
    • Can a user add/create items in the collection from the admin page for the collection OR do they have to be editing the collection to manage items?
• Settings
  • There was a discussion about whether to allow the collection creator to set things like nestable and discoverable.  Considerations:
    • These settings are generally determined by the collection type. 
    • If they are set on an individual collection, they can only become more restrictive.  For example, if the collection type says you can nest, then the individual collection can turn off nesting.  But if the collection type says you cannot nest, then the individual collection can NOT turn on nesting.
    • Are there any strong use cases for adding this level of complexity?  None were brought up.
    • Decision:  Do not add this until a strong use case is identified.  It will not be part of initial implementation.
  • If a collection can set a workflow to use for works created directly in the collection, there will need to be a place to identify the workflow.
  • Similarly, if a collection can set an APO to use as a template for created works, there will need to be a place to identify the APO settings.

...