Page History

...

• not just research anymore: photos, music, data sets, video, etc
  • More different kinds of content and metadata schemas
• research management systems
  • CRIS moves the repository to the back-end. As CRIS will be the front end
  • In edinburgh, PURE is being used with the LNI to ingest
  • Needs to support "whole research workflow", Grants, etc.
• simple (visual?) import – think dropbox?
  • Excel, Drag & Drop, minimal work to get things in
  • DepositMO
  • SWORD / SWORD2
  • ScottP: submission should be much much easier.
  • Bram: ScribD also had very easy upload, but poor in metadata. Nice feature in embedding lists & collections in other applications
• automated metadata capture
• content easy to use / reuse
• CRUD (needs to be able to easily Create, Read, Update, Delete – especially via web services, e.g. SWORD2, etc.)
• Support for branding / theming
• Support for Customizations (metadata and metadata structure)
• Various storage system integrations
• Flexible content workflows
• Support versioning / relationships
• flexible authorisation
  • give more control to user communities (do their own branding, etc)
• Support complex objects (representation of), both human- and machine-readable
• scientific data sets
• reporting (generate useful reports
• Support content reuse ("open" data)
  • e.g. embed info in dept website
• search (easy)
  • faceting / filtering (e.g. Solr)
• statistics: regular reports to item authors (like Digital Commons), plus usage/admin reporting
  • bot filtering (automatic?)
• getting stuff out
  • support disciplinary aggregation
  • creating adhoc "sets" of content
  • (this made me think of http://www.apsr.edu.au/orca/ - Kim)
• shareable metadata
  • different metadata "views"
    • shared version vs local use metadata
• new name (not "institutional repository"): maybe just "repository" or "storage"?
• support for preservation activities
• identifiers / persistance (flexible, granular, parts of items, people, collections)
  • the perils of handles...
  • DOIs vs Handles
  • Truly external IDs
• support access / privacy - making things "dark", either temporarily (embargo) or permanently
• "repository / DAM system that can display stuff vs. CMS that can do DAM"
  • do one thing, do it well
• flexible metadata schema
• dissemination
  • make data usable / able to be "mashed up"

...