[dspace-tech] SWORDv2 configuration error- Help!

We're attempting to enable the SWORDv2 endpoint in our DSpace instance for use in a DSpace-Symplectic Elements Repository Tools 2 integration. The service document gives this error: "Unable to recognise URL as a valid service document:..." Does anyone have any insight into what could be

Re: [dspace-tech] SWORDv2 configuration error- Help!

Andrea- Thank you so much for this tip! Uncommenting and standardizing the servicedocument.url property, plus one other minor change, fixed the problem. Keep up the good work! -GG On Wednesday, August 22, 2018 at 5:41:26 PM UTC-4, Andrea Schweer wrote: > > And further to that (having

[dspace-tech] URIs generating with 'http://localhost:8080' as root

Hello! We are very new to DSpace and operating on a limited technical staff. We have our DSpace up and running, but are running into a problem: The URIs are generating with "http://localhost:8080 /xmlui"

[dspace-tech] Example EPerson schema? Necessary EPerson schema fields?

Hey everyone- Our DSpace instance was initially set up by someone no longer employed at our institution. For whatever reason the EPerson schema reads like this: 194 eperson.javascript:alert(10379).1234

[dspace-tech] Institutions using SWORDv1 to ingest from ProQuest?

Hey Group- We're implementing a DSpace-based IR at my institution, and are interested in ingesting from ProQuest's ETD admin tool via the SWORDv1 protocol. Could anyone in this group direct us to any other institutions using such a workflow? So far we haven't been able to turn up any!

[dspace-tech] ORCID integration and DSpace versions- will it work pre-6.3?

Group- Will the procedure described in DSpace's ORCID integration wiki page work for version 6.2, or only version 6.3? I've heard that only 6.3 will work, since ORCID's version 1 API was depreciated. At the same time, I see no

Re: [dspace-tech] Re: Mapping ETD metadata sent from ProQuest to DSpace via SWORDv1

Tim- Thank you so much!! This is just the overview I needed to move forward. Keep up the good work! -Gabe On Thursday, December 13, 2018 at 2:04:19 PM UTC-5, Tim Donohue wrote: > > Hi Gabe, > > I don't have direct experience with mapping *ProQuest* fields into DSpace > fields. However, I

[dspace-tech] Re: Mapping ETD metadata sent from ProQuest to DSpace via SWORDv1

Checking one more time. Does anyone have experience using SWORD to crosswalk metadata? -Gabe On Friday, November 30, 2018 at 1:43:54 PM UTC-5, tuf0...@temple.edu wrote: > > To clarify what I mean by mapping, I mean mapping ProQuest ETD Admin xml > field 'X' to DSpace dublin core field 'Y'.

[dspace-tech] Mapping ETD metadata sent from ProQuest to DSpace via SWORDv1

Group- We've configured our SWORDv1 end and ProQuest has successfully delivered to our repository through it. ProQuest support is saying that mapping is done DSpace-side, rather than on their end, but I'm unclear on how this works. Could someone with more experience on the ProQuest->DSpace

[dspace-tech] Re: Mapping ETD metadata sent from ProQuest to DSpace via SWORDv1

To clarify what I mean by mapping, I mean mapping ProQuest ETD Admin xml field 'X' to DSpace dublin core field 'Y'.How would we get "//DISS_description/DISS_categorization/DISS_category/DISS_cat_desc" to map to "dc.subject" Thanks! -Gabe On Friday, November 30, 2018 at 1:38:25 PM UTC-5,

Re: [dspace-tech] A way to alter metadata values for display?

Terry- We are using DSpace 6.2 with XMLUI. We haven't selected a theme, but are interested in using one down the line, and it would be great to know how our selection would affect this. Thank you so much for your help! -Gabe On Thursday, January 10, 2019 at 9:46:44 AM UTC-5, Wenz,

[dspace-tech] A way to alter metadata values for display?

Group- Is there a straightforward way to hide the actual values contained in a field, while displaying translated or crosswalked versions of those values? We'd like to automatically translate two letter language codes into text: the language field would contain the value 'en' but display

[dspace-tech] Any way to switch item collection during metadata review (workflow tasks)

All- At our institution we'd like to set up a workflow where items are ingested into a single 'review' DSpace collection (from Symplectic Elements), then moved into another collection by a metadata reviewer as they're approved. Is there any way to do this through the Item submission

[dspace-tech] Outputting Qualified Dublin Core through DSpace's OAI- proper system configuration?

Group- We're configuring our DSpace and want to be able to output qualified Dublin Core through OAI. Would someone be able to give us an overview of how the system must be configured to do this? Should be putting field values exclusively in the 'dcterms' schema fields? Or, should we be

[dspace-tech] Strategies for granting anonymous, uni-affiliated users access to the submission form via Shibboleth

Group- At my University we'd like to take users directly from a Shibboleth authentication screen to the first page of the Submission User Interface (pictured in screenshot). We'd also like to, if possible: --Do this for three separate submission forms, one leading to a 'data' community,

[dspace-tech] Re: citation generation

Here is the relevant documentation: https://wiki.duraspace.org/display/DSPACE/Citation+Generation On Thursday, February 21, 2019 at 8:37:44 AM UTC-5, Muthuswamy N wrote: > > Hi, The link you have sent seems to lead to Dspace servlet engine. How is > this related to citation generation?

[dspace-tech] Re: Strategies for granting anonymous, uni-affiliated users access to the submission form via Shibboleth

Does anyone have any leads on this? On Wednesday, March 6, 2019 at 4:18:00 PM UTC-5, tuf0...@temple.edu wrote: > > Group- > > At my University we'd like to take users directly from a Shibboleth > authentication screen to the first page of the Submission User Interface > (pictured in

[dspace-tech] Auto populating a field with MIME types and/or file extensions pulled from 'provenance'?

Group- At my institution we're interested in populating a field with file extensions pulled from the automatically generated 'provenance' data. If possible, we'd also like to translate these into controlled MIME type values found in this list

[dspace-tech] Re: Auto populating a field with MIME types and/or file extensions pulled from 'provenance'?

Andrea- We're interested in a way to pull out just the file extension from the auto-generated field you've mentioned and put it programmatically in another field. Do you know of a way to do this? Thank you so much for the help you've already provided! -Gabe On Monday, January 28, 2019

[dspace-tech] Re: Auto populating a field with MIME types and/or file extensions pulled from 'provenance'?

Andrea- This is so helpful. Thank you!! -Gabe On Monday, January 28, 2019 at 3:48:24 PM UTC-5, tuf0...@temple.edu wrote: > > Group- > > At my institution we're interested in populating a field with file > extensions pulled from the automatically generated 'provenance' data. If >

[dspace-tech] Re: Integration with LCNAF via authority control- is it working??

Does anyone have any insight into this? Checking back in with the group. On Thursday, May 2, 2019 at 12:59:39 PM UTC-4, tuf0...@temple.edu wrote: > > Group- > > At my uni we'd like to Integrate our DSpace wtih Library of Congress Name > Authority File (LCNAF), as described on this

[dspace-tech] Re: Outputting Qualified Dublin Core through DSpace's OAI- proper system configuration?

Does anyone have any insight into this? Thank you in advance for your help! On Monday, April 8, 2019 at 11:30:00 AM UTC-4, tuf0...@temple.edu wrote: > > Group- > > We're configuring our DSpace and want to be able to output qualified > Dublin Core through OAI. Would someone be able to give us

[dspace-tech] Outputting Qualified Dublin Core through DSpace's OAI- proper system configuration?

Group- We're configuring our DSpace and want to be able to output qualified Dublin Core through OAI. Would someone be able to give us an overview of how the system must be configured to do this? Should be putting field values exclusively in the 'dcterms' schema fields? Or, should we be