Page History

...

• Basic Functionality:
  
  • Create, Read, Update Delete (CRUD) on objects
  • Versioning of objects
  • Basic Search & Browse functionality
  • Basic Preservation functionality (e.g. Fixity checks)
  • Basic Statistics (or "hooks" into external statistics engines)
• Content Model
  
  • Should support a Community & Collection "like" hierarchy 
    
    • Doesn't necessarily require Communities and Collections to be separate object types. They could just be a single "Container" type of object.
  • Items are the primary type of object.  Items include File(s).
    
    • Note: Old concept of "bundles" may need rethinking.
  • New object type:  Author objects
    (which hold metadata about authors/researchers in the system)
  • Persistent Identifier support for all objects
  • Support for object derivatives (e.g. thumbnail images)
  • More flexible relationships between objects
    
    • Including aggregations of objects & complex objects
• Metadata
  
  • Structured Metadata
  • Metadata should be at all levels of object hierarchy.
    
    • Administrative/Preservation Metadata at all levels, including on individual Files
  • Hierarchical Metadata formats should be supported
• Upload / Download of Content:
  
  • Self deposit & mediated (approval workflow based) deposit of content
  • Batch Deposit of content (from a UI)
  • Batch Download of content (from a UI)
  • Large File support for End Users
    
    • End Users should be able to upload and download large files themselves
• Access controls (Authentication & Authorization)
  • Authorization controls at all levels of object hierarchy
  • Also includes Embargo-style access controls
• User Interface Functionality
  
  • Single, default out-of-the-box User Interface
    
    • Preferably some sort of template-driven UI framework
  • User Interface should be "SEO Friendly"
  • Configuration Management takes place in the UI
  • UI Template/Theme Management takes place in the UI
• Standard Machine Interfaces
  
  • Some high priorities: OAI, SWORD, REST API
  • When possible, machine interfaces should be able to target content at any level (Community, Collection, Item, File, Author)
• Licensing support
  
  • Both deposit license and Creative Commons licensing
  • Enhanced "third party" licensing options, e.g. where a student deposits on behalf of a professor, or a librarian deposits ETDs on behalf of students.  Essentially, cannot always assume that the person depositing content has sufficient rights to accept a "deposit license" on behalf of actual author(s).  (Suggested by LibSkrat via Twitter)
    • Possibly related: "Depositing under an Open Access mandate", where there may be a required (configurable) license agreement based on either local or national OA mandate.
• Ability to easily "hook" into external tools & services
  
  • e.g. something like Curation Tasks & other more robust ways to integrate with other tools/services

...