| Create from Template | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Configuration and Enhancements
| Core Requirement | Summary Notes | /Decisions Priority level: Must have/Should have/Could have/Won't have (Services) | Back end or front end feature | Who can execute it? | Metadata or Services group? | Which system would this be done through | Back end or front end feature | Priority level: Must have/Should have/Could have/Won't have (Services) | Tickets | Notes/Decisions | Tickets | Reference links | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Standard repository features- front end | Searching, Facets, thumbnails, search results interface, item interface, customizable header footer and landing page | Must Have | Front | Devs or Gabe/Chin | S | Blacklight/DSpace custom/DSpace standard | Front | Must Have | ||||||||||||||
| DOIs- autogeneration | DOIs generated automatically, or at the push of a button | S: Must have M: Must have | Back | Gabe/Chin | S M | DSpace back end | Back | S: Must have M: Must have | Out of the box DOI integration: https://wiki.duraspace.org/display/DSDOC6x/DOI+Digital+Object+Identifier | |||||||||||||
| Customize Facets for display | Customizable facets | Must have | Front | Gabe/Chin | S | Blacklight/DSpace custom | Front | Must have |
| Procedure: https://wiki.duraspace.org/pages/viewpage.action?pageId=30218817 | ||||||||||||
| Citation generation | Automatic Citation generation, either via DSpace's native features or some sort of external plugin that functions through the interface | Should have | Unclear | Devs | S | Blacklight/DSpace custom/DSpace standard | Unclear | Should have |
| https://wiki.duraspace.org/display/DSPACE/Citation+Generation | ||||||||||||
| Direct Submission form- form | A direct submission form through which faculty can submit | GabeMust have | Back | Gabe/Chin | S | DSpace back end | Back | Must have |
| 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 | A way to authenticate users submitting through the form, probably via TUID/LDAP | External to DSpace in some regard. Must have | Back | Gabe/Chin | S | DSpace back end | Back | Must have | External to DSpace in some regard. |
| https://wiki.duraspace.org/display/DSDOC6x/Authentication+Plugins | |||||||||||
| Customizable Homepage | Customizable display layer, including homepage, subpage, configurable interface, customizable facets, etc. | Must have | Front | Devs Gabe/Chin | S | Blacklight/DSpace front end custom/DSpace front end standard | Front | Must have |
| '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 | ||||||||||||
| Documentation portal | A place to contain our policies and advisory text | Must have | Front | ? | S | Blacklight/DSpace front end custom | External to DSpace, as well as a part of the custom homepage | ? | S | Blacklight/DSpace front end custom | Front | Must have |
| |||||||||
| Customize simple item display- structural | Ability to customize the features of each page. For example, adjusting thumbnail size.Doable | Could have | Front | Devs Gabe/Chin | S | Blacklight/DSpace front end custom/DSpace front end standard | Doable out-of-the box up until a point. Would require dev support for more sophisticated integrations. | Devs Gabe/Chin | S | Blacklight/DSpace front end custom/DSpace front end standard | Front | Could have |
| Thread: https://groups.google.com/forum/#!searchin/dspace-tech/orcid|sort:date/dspace-tech/f_BZETZYXiM/mavRYst_AwAJ | ||||||||
| Visual improvements/aesthetic upgrades to the interface (search results, item view, and homepage) | Must have | Front | Devs | Blacklight/DSpace front end custom/DSpace front end standard | Front | Must have | ||||||||||||||||
| Customizable search results interface- structural | Could have | Front | Devs | Blacklight/DSpace front end custom/DSpace front end standard | Front | Could have | ||||||||||||||||
| View and download counts | Analytics integrated into front end | Configurable through Mirage2Must have | Front | Devs Gabe/Chin | S | Blacklight/DSpace front end custom | Front | Must haveConfigurable through Mirage2 |
| Documentation: https://wiki.duraspace.org/display/DSDOC6x/DSpace+Google+Analytics+Statistics RAMP: | ||||||||||||
| Analytics (back end) | Site admins can retrieve and run reports on analytics | Must have | Back | Gabe/Chin | DSpace back end | Back | Must have | |||||||||||||||
| Social media/Sharing buttons | Social media sharing buttons | Should have | Front | ? | S | Blacklight/DSpace front end custom | Front | Should have | Links/buttons for sharing work via social media (Twitter, Facebook/LinkedIn) | |||||||||||||
| Share via email button or function | Should have | Front | Devs | Blacklight/DSpace front end custom | Front | Should have | ||||||||||||||||
| New human-readable URL | Customizable URL | Must have | Back | Gabe/Chin | S | DSpace back end | Yes it's implementable. The Services group must decide on the URL | Gabe/Chin | S | DSpace back end | Back | Must have |
| |||||||||
| Thumbnails next to recently addedRequires customization of DSpace's front-end code | Could have | Front | Devs | S | Blacklight/DSpace front end custom/DSpace front end standard | Front | Could haveRequires customization of DSpace's front-end code | |||||||||||||||
| ADA note integrated into interface | Must have | Front | Devs | S | Blacklight/DSpace front end custom/DSpace front end standard | Front | Must have | |||||||||||||||
ORCID integration- front end | Green ORCID button linking back to author's ORCID profile, as in DukeSpace | Must have | Front | Devs | S | Blacklight/DSpace front end custom | Front | Must haveend custom | 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: | |||||||||||||
| collating fields in advanced search | Combining two fields separated on the back end for practical reasons into a single field in the advanced search UIDefinitely a developer task | Should have | Back | Devs | M | DSpace back end | Back | Should have | Definitely a developer task | See: http://kim-shepherd.blogspot.com/2010/11/discovering-discovery-dspace-solr-tips.html | ||||||||||||
| Transform language codes (or any metadata value) into full words via display layer | the field contains the value 'en' but the interface displays the word 'English' | Must have | Front | Devs | M | Blacklight/DSpace front end custom/DSpace front end standard | 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 Note that this could be done easily by adding another language field specifically for display, however the metadata group would prefer to avoid this | Devs | M | Blacklight/DSpace front end custom/DSpace front end standard | Front | Must have | Thread on the topic: | |||||||||
Auto-Generate MIME types | Automatically populate a field with MIME type values based on file extensionLast option- contact Texas Uni | Should have | Back | Devs | M | DSpace back end | Back | Should haveLast option- contact Texas Uni | See convo with Andrea SchweerNotes from Services Metadata meeting: This will impact how cumbersome the workflow is for the IR manager. How cumbersome will depend on the volume of submissions, which is currently unknown. | |||||||||||||
| SWORD mapping from ProQuest | Automatic ingests of ETDs and associated metadata from ProQuest, plus mapping | Should have | OngoingBack | Gabe/Chin/Holly Possibly Devs | M | DSpace back end | BackOngoing | Should have | DSpace METS SIP Profile: https://wiki.duraspace.org/display/DSPACE/DSpaceMETSSIPProfile | |||||||||||||
Extend embargo functionality | Must have | Back | Gabe/Chin | M | DSpace back end | It can easily be enabled in the submission form. To auto-apply embargos via imported ProQuest metadata we need to provide an exact lift date. Two additional back-end fields must be implemented, embargo.field.terms and embargo.field.lift. Note that there may be an exact date in the regular metadata from proquest ETD admin | Gabe/Chin | M | DSpace back end | Back | Must have | Embargo documentation https://wiki.duraspace.org/display/DSDOC6x/DSpace+6.x+Documentation Implement a variation on this for 'six month', '1 year', etc.: http://wiki.lib.sun.ac.za/index.php?title=SUNScholar/Embargo_Systems/1.8.X Embargo setter javascript: https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/embargo/DefaultEmbargoSetter.java | ||||||||||
| CVs- internal list | Must have | Back | Gabe/Chin | M | DSpace back end | Back | Must have | https://wiki.duraspace.org/display/DSPACE/Authority+Control+of+Metadata+Values | ||||||||||||||
| CVs- external lookup (via something like LCSH)via something like LCSH) | Could have | Back | Gabe/Chin | M | DSpace back end | |||||||||||||||||
| CVs- ORCID | Could have | Back | Gabe/Chin | M | DSpace back end | Back | Could have | CVs- ORCID | Should be straightforward Note: The Services group's ORCID enhancement depends on this. | Gabe/Chin | M | DSpace back end | Back | Could have | https://wiki.duraspace.org/display/DSDOC6x/ORCID+Integration | |||||||
| Mirage2 theme-implement | Customizable display layer, including homepage, subpage, configurable interface, customizable facets, etc. | NA | Front | Gabe/Chin | SNA | Front | NA |
| 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 | |||||||||||||
| DOI patch | Fix for 6.x DOI prob | NA | Back | Gabe/Chin Maybe devs | S M | NA | BackNA | Thread on the issue: https://groups.google.com/forum/#!topic/dspace-tech/EQUlVrif-u8 The old DIM2DataCite.xsl crosswalk: https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/DIM2DataCite.xsl Patched DIM2DataCite.xsl crosswalk: https://github.com/DSpace/DSpace/pull/2321/commits | ||||||||||||||
| Upgrade to 6.3 | NA | Back | Gabe/Chin | M S | NA | Make a backup plan and implement first. Use Meld to find versions of our file | Gabe/Chin | M S | NA | Back | NA | 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 |
...
| 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? |
...