| Create from Template | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Configuration and Enhancements
| Core Requirement | Notes/Decisions | Who can execute it? | Metadata or Services group? | Priority level 1-5 low to high (Services) | Jira Tickets | Reference links | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Blacklight-based wrapper/presentation layer | Devs | S | ||||||||||||
| Mirage2 theme-implement | Gabe/Chin | S |
| Meeting Example: https://atmire.com/preview/browse?type=title See note on this page, specifically 'Enabling and building the DSpace 5 Mirage 2 theme' for troubleshooting ideas Thread on error encountered by Chin, with Fix by Tim Donohue | ||||||||||
| Customize Facets for display | Gabe/Chin | S |
| Procedure: https://wiki.duraspace.org/pages/viewpage.action?pageId=30218817 | ||||||||||
| Citation generation | Devs | S |
| https://wiki.duraspace.org/display/DSPACE/Citation+Generation | ||||||||||
| Direct Submission form- form | Gabe/Chin | S |
| Documentation: https://wiki.duraspace.org/display/DSDOC6x/Submission+User+Interface Input forms customized via: https://github.com/DSpace/dspace-release/blob/master/config/input-forms.xml (The form-map maps collection handles to forms.) Item submission process customized via this: https://github.com/DSpace/DSpace/blob/master/dspace/config/item-submission.xml (The process-map maps collection handles to a particular Item Submission Process.) slide deck: https://www.slideshare.net/bramluyten/secrets-of-the-dspace-submission-form | ||||||||||
| Direct Submission form- Public access via web | External to DSpace in some regard | Gabe/Chin | S |
| https://wiki.duraspace.org/display/DSDOC6x/Submission+User+Interface | |||||||||
| Homepage customized | Devs Gabe/Chin | S |
| 'Making DSpace your own' webinar https://www.slideshare.net/DuraSpace/42418-making-dspace-your-own-webinar-recording Here's the custom code from the webinar | ||||||||||
| Wiki for documentation | External to DSpace, as well as a part of the custom homepage | ? | S |
| ||||||||||
| Customize simple item display | Doable out-of-the box up until a point. Would require dev support for more sophisticated integrations. | Devs Gabe/Chin | S |
| Thread: https://groups.google.com/forum/#!searchin/dspace-tech/orcid|sort:date/dspace-tech/f_BZETZYXiM/mavRYst_AwAJ | |||||||||
| Analytics (for entire repository and for individual items) | Configurable through Mirage2 | Devs Gabe/Chin | S |
| Documentation: https://wiki.duraspace.org/display/DSDOC6x/DSpace+Google+Analytics+Statistics RAMP: | |||||||||
| Social media/Sharing | ? | S | Links/buttons for sharing work via social media (Twitter, Facebook/LinkedIn) | |||||||||||
| New human-readable URL | Yes it's implementable. The Services group must decide on the URL | Gabe/Chin | S |
| ||||||||||
| Thumbnails next to recently added | Requires customization of DSpace's front-end code | Devs | S | |||||||||||
ORCID integration- front end | Devs | S | Cambridge: https://www.repository.cam.ac.uk/handle/1810/266430 Duke: https://dukespace.lib.duke.edu/dspace/handle/10161/8875 DSpace orcid documentation: https://wiki.duraspace.org/display/DSDOC6x/ORCID+Integration Thread on v6.2 compatibility and 6.3 errors https://groups.google.com/forum/#!topic/dspace-tech/N_azMfWalD8 GG's orcid doc: https://docs.google.com/document/d/1ump6tlTrd62nvDoXo4I9GBsSdLs5SeY7k1flP2InYTs/edit 6.3 errors doc: | |||||||||||
| ORCID integration- back end | Gabe/Chin | M | ||||||||||||
| Combining fields in advanced search | Definitely a developer task | Devs | M | See: http://kim-shepherd.blogspot.com/2010/11/discovering-discovery-dspace-solr-tips.html | ||||||||||
| Transform language codes into full words via display layer | This is doable through the tweaking of the native theme or another theme like Mirage2. I was unable to find a way to do this other than through the theme? | Devs | M | Thread on the topic: | ||||||||||
| SWORD mapping from ProQuest | Gabe/Chin/Holly | M | DSpace METS SIP Profile: https://wiki.duraspace.org/display/DSPACE/DSpaceMETSSIPProfile | |||||||||||
| Extend embargo functionality | This will need developer support if we're going to use ProQuest's numerical codes. | Devs | M | Embargo documentation https://wiki.duraspace.org/display/DSDOC6x/DSpace+6.x+Documentation | ||||||||||
Auto-Generate MIME types | Devs | M | See convo with Andrea Schweer | |||||||||||
| Controlled Vocabs | Gabe/Chin | M | https://wiki.duraspace.org/display/DSPACE/Authority+Control+of+Metadata+Values | |||||||||||
| Upgrade to 6.3 | Make a backup plan and implement first. Use Meld to find versions of our file | Gabe/Chin | M S | Note: DSpace 7.0 will be released mid 2019 https://www.youtube.com/watch?v=JBH0A3QwBUk . (see 18:36 for directories to back up... back up a) sql and solr databases. see 20:30, section on using meld to discover differences. 23:50 for folders to check for changes) | ||||||||||
| More Issues | See Jira Board |
High level requirements
| Core Functionality | Requirements | Notes/Decisions | Jira Tickets | Reference Links | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Integrate Elements and DSpace via the Repository Tools 2 connection |
| The systems are integrated and communicating This task is complete in Dev. Configuration can be ported to Prod once the two systems' configurations are OKed by IR Services group |
| |||||||||||||||||
DOIs |
| See the 'DOI functionality' section of this page |
| |||||||||||||||||
| ETDs |
| See the 'ETD functionality' section of this page |
| |||||||||||||||||
| DSpace structure/configuration |
| See the 'DSpace Structure' section of this page |
| |||||||||||||||||
| Metadata configuration |
| See the 'Metadata configuration' section of this page |
| |||||||||||||||||
| Back-end configuration |
| See the 'Back end Configuration' section of this page | ||||||||||||||||||
Budget | Determine:
|
...
| Core Functionality | Requirements | Complications and question: | Notes/Decisions | Jira Tickets | Reference Links | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DOI generation | DOI agency integrated with DSpace | DSpace, when configured so that DOI generation is integrated, automatically generates a DOI for each item added to the repository.
|
| ||||||||||||||||||
| DOI generation | Manual retrieval and entry of DOIs | How would manual generation of DOIs through a new Libraries CrossRef membership work? This would be the simplest solution, however would require more manual intervention per-item.
| |||||||||||||||||||
Subscribing to a DOI Registration agency | We'll need to join a DOI registration service |
|
| ||||||||||||||||||
| DOIs for data | Decide if we want DOIs for data |
|
...
| Core Functionality | Requirements | Complications and question: | Notes/Decisions | Jira Tickets | Reference Links | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Elements Deposit interface- customize statements | Guidance text- we'll need to provide a statement Institutional Advice- we'll need to provide a statement |
| https://docs.google.com/document/d/1p57lEx70eWyYMhd_EIAias7f9-H-U7Ecb8pKpLnsJ-E/edit | ||||||||||
DSpace- licenses | Customize license for Elements→DSpace submission workflow | We may not have to use this... the interface a faculty submitter will have to use is the Elements interface | |||||||||||
| DSpace- licenses | Customize license/advisory text for Direct Submission→DSpace workflow | ||||||||||||
| ADA policies | Determine what they are and how they affect our configuration | A text readable layer is required on all digital objects. This means that the ETD PDFs will have to be OCRed, as well as PDFs ingested via Elements. |
Workflow considerations
| Core Functionality | Requirements | Complications and question: | Notes/Decisions | Jira Tickets | Reference Links |
|---|---|---|---|---|---|
| Implementation of 'deposit' button in Elements | a deposit embedded in the Elements interface, usable by both library staff and faculty users of our RIMS | It must be enabled universally. Is this a problem? This functionality cannot be limited only to certain classes of user. The crosswalk allows us to move items deposited from Elements→DSpace to specific dspace collections based on their 'publication type' status in elements. This could be one solution. | |||
Library mediated deposits from Elements→DSpace | We've discussed having the library deposit from Elements to DSpace on faculty member's behalf. | One complication is that Elements indexes articles hosted in other systems, but does not ingest copies of articles. What are the workflow and legal implications of downloading these articles directly from the publication. Another complication is that many journals allow the deposit of the preprint or accepted version, but not the publisher's version. How would we obtain one of the permissible versions, which would be unpublished. | |||
| Dark archive? | We could set up a DSpace collection shielded from the public that would facilitate the long term preservation of faculty research, while keeping it in accessible due to legal complications | Is this worth it? Is this too far in the wrong direction re: open access? |
...