Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated charter structure

Functional requirements and/or policy related to management of assets and entities within the repository (assets, users, permissions, metadata, policies), reporting and tracking, staff-facing interface needs will be listed here. 

Charge/Deliverables:

  1. Develop personas user profiles for staff users managing repository entities.Work with Library Web & UX Strategy team to generate wireframes for staff management interface
  2. Create matrix of entities, roles, activities and user stories to articulate Management activities and permissions:
    • In conjunction with the
    repository architecture
    • Repository Architecture group, identify management activities performed on repository entities (objects, collections, files, policies, agreements, etc.: creating, editing, deleting, triggering preservation actions
    )
  3. Develop requirements for search and display of repository entities within a management system context
  4. Gather requirements for external identifier management (e.g. DOIs, ORCIDs, ISNIs)
  5. Outline needs for users/permissions management within a management application (users, groups, roles, etc.)
  6. Develop requirements for reporting (e.g. inventory, storage projections, staff activity, throughput: turnaround for ingest/process materials; volume of work
    • )
    • In conjunction with Repository Architecture group, determine staff needs around managing versions of content (e.g. metadata versioning; file versioning; whole object versioning; object restoration)
    • Outline needs for users/permissions management within a management application (users, groups, roles, etc.)
    • In coordination with the Deposit group, identify access controls and roles needed to support deposit and approvals
    • In conjunction with the
    Access team
    • Content Display FRG and DCSC, determine requirements for access controls for discovery, viewing, downloading, embargoes, and leases.
  7. Develop requirements for search and display of repository entities within a management system context
  8. Develop requirements for reporting (e.g. inventory, storage projections, staff activity, throughput: turnaround for ingest/process materials; volume of work)
  9. Gather requirements for external identifier management (e.g. DOIs, ORCIDs, ISNIs)
  10. Coordinate Emory representation in related Hydra Samvera Working Groups/Interest Groups