Page History

• Basic version of this use case is already implemented as Importing and Exporting Items via Simple Archive Format
• But, this particular use case is asking for an easier route to Batch Deposit, via CSV.  Could be implemented via using some of the CSV code in Batch Metadata Editing (which is a good example of basic deposit via CSV)

• Basic version of this use case already exists in Discovery 
• This particular use case implies some enhancements / cleanup

• Use case describes a problem with how contributors are treated in DSpace (via Discovery)
• Suggests an "Author Profile" page, which is related to both the @mire "Author Profiles" module and DSpace-CRIS

• Already possible in DSpace, but it's not an "easy" thing to configure
• Related to Discovery and Authorization / Access rights in general

Goal 1: Fundamentals of IR

Goal 5: Low cost, "just works"

• Relates to the following:
  • Versioning of Items
  • Authorization / Access rights in general
• Variation on use case: Item editing by original submitters

• Relates to the following:
  
  • Media Filters
  • Submission UI

• Relates to the following:
  • Discovery
  • Themes (especially Mirage2 / JSPUI on bootstrap)

• Deposit interface already exists obviously, but this implies several enhancements
• This might be as simple as cleaning it up and making it easier to use (with tooltips, etc), and adding more HTML5 functionality (e.g. drag and drop)
• Loosely related to Admin UI - Aids and tooltips in the UI

Goal 1: Fundamentals of IR,
Goal 4: Integration with external services

• Seems like it could be easily implementable by simply hyperlinking author names, subjects and linking them to searches on those "facets" in Discovery

• Already exists to some extent in the existing CC Licensing deposit step. Unclear what enhancements would be implied to the existing functionality

• Great idea. But may require locating tools that can either be redistributed freely, or turning this into an optional module (which requires additional tools be installed)

Goal 5: Low cost, "just works"

• Seems like it could be easily implementable in Discovery

• Related to Item Versioning
• Variation on use case: Crowdsourcing metadata for archived items (but seems less popular than this other use case)

• Already exists in Discovery, but may require some minor enhancements to how searches work in Discovery

• Closely related to use case: Visitor can play media hosted on an external streaming media server
• Would require locating tools that can either be redistributed freely, or turning this into an optional module (which requires additional tools be installed)

• Closely related to use case: Streaming Video Content
• Would require locating tools that can either be redistributed freely, or turning this into an optional module (which requires additional tools be installed)

• Unclear how popular this is. Could it be as simple as selecting a collection "type" (textual, image-based, etc) to enable different "themes"?

• May have overlap with use case: Visual collection browsing

• Associated with use cases on Format identification and Format validation
• May be easier to implement as an integration with an external service/tool

• Would need to be an integration with an external service/tool

• Seems like an obvious "win".  Would also be usable in End User interfaces (like Deposit). See also End User - Easy and Intuitive Deposit Interface

• Directly related to existing "Batch Metadata Editing" feature (which is currently Admin only though)

Theming , Configuration

Configuration, Deposit

Deposit,
Incomplete

• Currently flagged as incomplete simply cause this use case has no details, so it's difficult to determine if it's fully "met" by the software

• Existing Checksum checker & reporter does some of this, but not in UI

• Current format identification is rudimentary (based on file extension). This has been an issue for some time

Goal 1: Fundamentals of IR

• Is this something DSpace should do by default? Or should this really be an optional module which connects to an external service to perform validation?

Goal 4: Integration with external services

• Currently no easy way to perform moves of Communities or Collections, except via DB editing.

• Exists in DSpace, but not an easy task to perform

• Unclear how frequently such changes would need to be made. So, may not be a high priority for Admin UI quite yet.

• May need some more specific use cases (types of reports, etc), as there's a lot of possibilities here

• Directly related to making "Batch Metadata Editing" easier. You can manually delete fields after CSV export.

• Subset / Duplicate of Configurations in the admin UI

• Subset / Duplicate of Customise which metadata fields to facet upon, search upon

Configuration , Browse/Search

• Duplicate of Configurations in the admin UI

• DSpace already has some built in Embargo options. But, as Embargoes seem to be a hot topic, might be worth reviewing what enhancements are needed.

• Subset / Duplicate of Use Case Batch Deposit

• Dependent on Basic Preservation - Format identification

• Unclear how popular / common this use case is

• Related to Configurations in the admin UI and Manage input forms

• Closely compliments / relates to Customise which metadata fields to facet upon, search upon

Configuration, Deposit

• Related to Configurations in the admin UI

Duplicate

• Duplicates Admin UI - Change community/collection parent/child relationship

• Duplicates Admin UI - Change community/collection parent/child relationship

• Related to Admin UI - Collection Admin can construct a Quality Control report

• Related to Admin UI - Manage Indexes/Indexing

• Related to Admin UI - Clear the OAI Cache

• Duplicates End User - Batch Deposit

• Related to Admin UI - Apply an existing theme to a collection or community through the GUI

• Complimentary to / dependent on Admin UI - Theme management

• Closely related to Admin UI - Rebuild the discovery index (but for specific collections only)

• Related to End User - Batch Deposit
• If a Batch Deposit has you verify the batch prior to deposit, this "undo" may be less necessary.

• As noted in use case, already possible in Configurable Workflow. But not easy in the default "workflow".

• This is more of a bug report, but likely one to resolve

• Relates to alerting an admin to possible configuration
• Some alerts may be easier to implement than others

• While this is of high interest, one might question whether DSpace can ever do this "well enough", or if it's better to rely on an integration with an external statistical engine (e.g. Google Analytics)
• A few of these use cases though might be relatively easy to add into existing Solr-based Statistics (e.g. referrer info).

• This is essentially a feature request / configuration request, but still seems to be a reasonable one.

• The basis for these use cases are in the existing Solr Statistics. But, there's several enhancements / reports that are new.
• Ranked as one of the highest features in Vision Survey

• Already implemented through LDAP, Shibboleth, and CAS support.
• Perhaps needs OAuth support in the future?

• Not only integrate with external authentication services, but allow multiple external authentication options on a single service.
• Already implemented via Authentication Plugin mechanism?

• Quite tricky. May be hard to match metadata sources. Some sources may need a subscription.
• Perhaps easier to implement through a method such as "Provide DOI, DSpace will find all the metadata"

• Adding CrossRef DOI support

• Overlap with lots of 'deposit' use cases
• Can be implemented via SWORD? Perhaps therefore not a DSpace requirement as such?

• Could be performed using LTI (Learning Tools Interoperability)
• Or could be implemented with a simple 'share this' type of approach

• Embed a document viewer such as the Wellcome Library Player (http://www.wellcome.ac.uk/News/Media-office/Press-releases/2014/WTP055613.htm)

• This could be implemented as a pull from an external system, or as a push from the the external system.
• Maybe SWORD deposit, or OAI-PMH harvesting

• Overlaps with a lot of other content harvesting or deposit use cases
• Hard to describe as it could vary in so many ways according to the institutional setup of systems

• Could be as simple as ensuring there is an OAI-PMH interface for harvesting the content into external search systems or aggregators

• External harvest of other sources, e.g. via the existing OAI-PMH harvest functionality

• Either basic links to an external resolver / geo parser, or better in-built handling of geo data (PostGIS?)

• Would ORCIDs be implemented using the current controlled authority plugin system?

• Implement a link to ORCID identifiers. Include the ORCID in the user profile, but cache supplemental information in an index such as solr

• Include ORCID identifiers in the batch CSV editing functionality.
• Need to decide how to relate ORCIDs to author name strings in the DSpace data model, and then how to represent those in the CSV.

• Implemented already

• Two aspects to this: different identifiers (DSpace now supports DataCite), but also identifiers for more than just items, for example for bitstreams

• Full REST API allowing all CRUD functions, not just READ operations

• Ensure DSpace works in the wider scholarly systems landscape
• ResourceSync not yet core in DSpace distribution

• Ensure DSpace user interfaces maintain best practice in this area