Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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 for staff users managing repository entities.
  2. In conjunction with the 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)
  7. 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)
  8. In coordination with the Deposit group, identify access controls and roles needed to support deposit and approvals
  9. In conjunction with the Content Display team and DCSC, determine requirements for access controls for discovery, viewing, downloading, embargoes, and leases.
  10. Coordinate Emory representation in related Hydra Working Groups/Interest Groups
  • No labels