Page History
...
Info |
---|
This page provides an analysis and prioritization for the Use Cases gathered via the 2014 Vision Survey and later DCAT Use Case gathering meetings. A few notes on this analysis: Priorities are in "draft" form, but have been assigned based on a combination of three factors:
Complexity is also in "draft" form and is based on the current state of the codebase. As such, it may change drastically for some use cases based on the eventual 2015-16 Technical RoadMap document. For example, a use case which already exists or "mostly" exists may be ranked as "Low". But if the RoadMap recommends rebuilding/refactoring related features/dependencies, its complexity may increase to "Medium" or "High". Core / Non-Core specifies whether a given Use Case seems to be a "core" use case or "non-core" (Note: non-core does NOT mean this feature shouldn't be possible in DSpace. Rather, it just means that it likely should be provided either via an extension or integration to the "core" of DSpace). |
Advanced Tables - Table Plus | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
...
|
...
...
...
...
|
...
...
...
...
|
...
...
...
...
|
...
...
...
...
|
...
...
|
...
...
...
...
|
...
...
...
...
|
...
|
...
...
...
...
|
...
|
...
|
...
|
...
|
...
...
|
...
- 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
...
- Seems to be highly related to the first story in Stats/Metrics - Advanced Statistics
...
- Seems like an improvement to Basic Stats
- Added as a child to Basic Statistics
...
- Seems like an improvement to Basic Stats
- Added as a child to Basic Statistics
...
- Seems like an improvement to Basic Stats
- Added as a child to Basic Statistics
...
- Seems like an improvement to Basic Stats
- Added as a child to Basic Statistics
...
- Seems like an improvement to Basic Stats
- Added as a child to Basic Statistics
...
- Seems like an improvement to Basic Stats
- Added as a child to Basic Statistics
...
- Seems like an improvement to Basic Stats
- Added as a child to Basic Statistics
...
- Seems like an improvement to Basic Stats
- Added as a child to Basic Statistics
- As implied in use case, may need to be configurable
...
- Related to Stats/Metrics - Filter Usage by Referrer Domain as well
...
- 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
...
|