Page History

...

• Metadata for All Objects: In the Developers Meeting on Jan 30, 2013, those in attendance discussed a need to release an updated version of this "Metadata for All" pull request (#12).  However, we may need the following:
  
  • An updated version of the pull request based on current "master"
  • We like the suggestion to rename "schemas" to "namespaces"
  • We'd like it to use "metadatavalue" (and similar) tables rather than creating a new set of Metadata tables specific to other objects.   We understand this may be more disruptive, but it seems odd to have different metadata namespaces
  • If possible we'd want this change to be "backwards compatible" with existing UIs. The goal would be to perform this change in stages – first update the APIs to allow for metadata on all objects, then update each UI one-by-one.  Hopefully we can get all of the UIs done before 5.0
  • We also obviously could use some basic documentation / overview of the thinking behind it, so that we can vote this through sooner rather than later.
• REST API updates
• Audio/Video Streaming (RTMP, HLS, DASH) Support
• Replace Authentication and Authorization code in DSpace with a 3rd-party framework 
• DSpace/ORCID Integration XMLUI (University of Missouri - @mire)

• Jira
  server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2052

   (The World Bank - @mire)
  

• Jira
  server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2053

   (@mire)
  

• Jira
  server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2061

   (pbecker)

Possible JIRA tickets to resolve (automated list)

...