Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Issue 1 of the Collection Extensions blog

Collection Extensions is an effort to create a consistent and flexible approach for grouping items in Hyrax repositories.  Implementation sprints are beginning Aug 7, 2017 (sign-up).

...

Use Cases

What is your use case for collecting together works?  The Collection Extensions Requirements Working Group identified several use cases.

...

  • assign Collection Managers (groups or users) who can edit collections other users have created, including adding to and removing works from a collection, modifying collection metadata, and deleting collections
  • assign Collection Creators (groups or users) who can create and manage their own collections


Footnotes:

1  Based on use cases identified so far, it is expected that the number of collection types will be less than 5.  If you have a use case requiring more, please let me know.  A large number of collection types has an impact on UI design.

2  The only use case identified for required membership is Admin Sets.  Let me know if you have a use case for more than one collection type in a system requiring membership (i.e., all works must be a member of collection type Admin Set AND all works must be a member of collection type A).

3  The Advanced configurations are not expected to be part of the original sprint.  More information on these will be included in a later blog post.


Basic Configuration Process

...

In this definition of Exhibit type, Exhibit collections create a grouping of items for display to public users.


Current User Collection features (for reference)

User Collections for a self-deposit site

User Collections in a staff curated site

Exhibit
  •  NESTABLE
  •  MULTIPLE MEMBERSHIP
  •  DISCOVERY (public by default)
  •  SHARING
  •  REQUIRE MEMBERSHIP
  •  NESTABLE
  •  MULTIPLE MEMBERSHIP
  •  DISCOVERY
  •  SHARING
  •  REQUIRE MEMBERSHIP
  •  NESTABLE
  •  MULTIPLE MEMBERSHIP
  •  DISCOVERY
  •  SHARING
  •  REQUIRE MEMBERSHIP
  •  NESTABLE
  •  MULTIPLE MEMBERSHIP
  •  DISCOVERY
  •  SHARING
  •  REQUIRE MEMBERSHIP


For a self-deposit site, there may be only one collection type defined, that is, the User Collections for a self-deposit site.

...

Admin Sets can be viewed as a collection type.  For the initial implementation, the code controlling and managing Admin Sets will remain the same.  Sites cannot change the configuration of Admin Sets.  The configuration is defined by the code implementing the behaviors of Admin Sets.  Effectively, the configuration is...

Admin Sets (effective) configuration
Basic:
  •  NESTABLE
  •  MULTIPLE MEMBERSHIP
  •  DISCOVERY (optional)
  •  SHARING
  •  REQUIRE MEMBERSHIP

Advanced:

  •  WORKFLOW
  •  VISIBILITY
  •  CONTROL VISIBILITY


UI changes

Since these configurations and the grouping functionality is consistent with the concept of Collections, the UI is being adjusted to show Admin Sets to users as though they were implemented as just another collection type.  The UI adjustments include...

...

You can continue to update Managers and Creators.  And you can continue to add a new collection type, if needed.This is the first of several blog posts intended to raise awareness of the implementation effort to expand the functionality of collections.  Please don't hesitate to ask questions and get clarifications.  That will allow for better communication and solidify the design.


...