Re: [dspace-tech] DSpace 7.6.1 ORCID integration / Synchronization settings ERROR

[Sean Kalynuk]

Hi Matthias,

Regarding the error “The update of the synchronization settings failed”, this 
has been documented as part the following issue:

https://github.com/DSpace/DSpace/issues/8925

Locally, I applied the source code fix as described in a comment from that 
issue https://github.com/DSpace/DSpace/issues/8925#issuecomment-1617623431 and 
it resolved that particular problem for us (at least it did with 7.5).

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Matthias Letsch 
Date: Thursday, June 13, 2024 at 10:32 AM
To: DSpace Technical Support 
Subject: [dspace-tech] DSpace 7.6.1 ORCID integration / Synchronization 
settings ERROR
Caution! This message was sent from outside the University of Manitoba.

Hello there,

I managed to activate ORCID integration in a test environment with connection 
to the ORCID sandbox api. (I'm only interested in the Profile and 
synchronization part, not the ORCID authentication method). Unfortunately, when 
I try to update ORCID synchronization settings, I get a error message.
So what I did:
1. Enable configurable entities 
(https://wiki.lyrasis.org/display/DSDOC7x/Configurable+Entities) and Enable 
Researcher profiles 
(https://wiki.lyrasis.org/display/DSDOC7x/Researcher+Profiles)
2. Get ORCID sandbox credentials 
(https://info.orcid.org/documentation/integration-guide/sandbox-testing-server/)
 and enable ORCID integration by setting properties in local.cfg / 
modules/orcid.cfg (https://wiki.lyrasis.org/display/DSDOC7x/ORCID+Integration)
3. Log in as test person, claim an existing Person entity as Researcher 
Profile, connect the profile to sandbox orcid id. <-- Everything worked so far.

The DSpace ORCID page now states the following:
Granted Authorizations: Get your ORCID ID
Missing authorizations: " Great! This box is empty, so you have granted all 
access rights to use all functions offers by your institution."

The Error
When changing values in ORCID Synchronization settings and clicking on "Update 
settings", an error message appears "The update of the synchronization settings 
failed"

The dspace logs tell me the following:
2024-06-13 17:20:41,332 WARN  unknown unknown 
org.dspace.discovery.SolrServiceImpl @ We have a collection or community admin 
with ID: 6edd60e9-9457-4ec7-91a0-cbaefec205e2 without any administrable 
collection or community!
2024-06-13 17:20:41,363 WARN  unknown unknown 
org.dspace.discovery.SolrServiceImpl @ We have a collection or community admin 
with ID: 6edd60e9-9457-4ec7-91a0-cbaefec205e2 without any administrable 
collection or community!
2024-06-13 17:20:41,369 INFO  f70163a4-0bc1-4d1d-a361-1601ecfd846b 
98ac4304-eeaf-4c3c-96ba-3d575a332afb 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET 
/server/api/eperson/profiles/6edd60e9-9457-4ec7-91a0-cbaefec205e2] originated 
from /entities/person/08715eca-330f-4798-91e6-91a476dafce7/orcid
2024-06-13 17:20:41,501 WARN  unknown unknown 
org.dspace.discovery.SolrServiceImpl @ We have a collection or community admin 
with ID: 6edd60e9-9457-4ec7-91a0-cbaefec205e2 without any administrable 
collection or community!
2024-06-13 17:20:41,532 WARN  unknown unknown 
org.dspace.discovery.SolrServiceImpl @ We have a collection or community admin 
with ID: 6edd60e9-9457-4ec7-91a0-cbaefec205e2 without any administrable 
collection or community!
2024-06-13 17:20:41,546 INFO  f70163a4-0bc1-4d1d-a361-1601ecfd846b 
b945ba4b-b7e8-46e4-8a6f-3d28184cc02a 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [PATCH 
/server/api/eperson/profiles/6edd60e9-9457-4ec7-91a0-cbaefec205e2] originated 
from /entities/person/08715eca-330f-4798-91e6-91a476dafce7/orcid


This ID belongs to the user with whom I am testing the Orcid link and want to 
update the settings. So that reads as follows for me: Users who link their 
profile to ORCID need certain rights to at least one collection or community 
for the ORCID synchronization to work. Do I understand that correctly?

As an admin, how do I assign these rights to users? Can I automate this or do I 
have to manually give each user with an ORCID link rights to a collection? I 
don't quite understand this yet. Does anyone have any experience with ORCID 
integration and can help me here?

Many thanks and best regards
Matthias

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/ddd09eed-5daf-438f-b4e7-657b68d9a173n%40googlegroups.com.

Re: [dspace-tech] Re: sword fails authentication for DSpace 7.6.1

[Sean Kalynuk]

Make sure that if you’re using SWORDv1, the account may require ADMIN 
privileges on the collection due to this bug:

https://github.com/DSpace/DSpace/issues/8647

Simply adding the user to a SUBMIT group will not work. I have seen this in our 
DSpace 7.5 instance.

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Joyner Library 
Date: Tuesday, June 11, 2024 at 1:15 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] Re: sword fails authentication for DSpace 7.6.1
Caution! This message was sent from outside the University of Manitoba.

Hi All,

Creating an account through CLI allowed me to download the service document. 
Vireo 4 is happy and able to deposit dissertations using SWORD client.

Thank you!

On Monday, June 10, 2024 at 3:23:56 PM UTC-4 mw...@iu.edu wrote:
On Fri, Jun 07, 2024 at 08:46:27PM +, DSpace Technical Support wrote:
> I think the answer may be that SWORD doesn't support LDAP authentication (and 
> it looks like that's what you are using based on the logs you shared). SWORD 
> *only supports* PasswordAuthentication (DSpace's internal authentication 
> system). So, to login to SWORD, you'd need to use an internally stored 
> username & password.
>
> Tim

There's the today answer (use password authentication) and there's the
todo answer (this should not have errored, and probably should not
have failed).

LDAP authentication as implemented in DSpace uses a username/password
pair so, if this isn't working, it's probably broken rather than
impossible. The result is an NPE, which IMHO is always an indicator
of code that needs fixing. The site of the NPE from the stack trace
should suggest how we came to be setting attributes on a nonexistent
request. Although it seems fairly obvious:
'o.d.sword.SWORDAuthenticator.authenticates' passes a null
'HttpServletRequest' to 'AuthenticationService.authenticate', and that
service would pass it on down to 'LDAPAuthentication.authenticate' if
so configured.

(Noted in passing: there's another class o.d.sword.SWORDAuthentication
with an identically named method, which class seems to be used nowhere
in DSpace.)

We need a Github Issue for this. It's probably best if it comes from
someone who's actually observed the problem and can provide logs.

> On Tuesday, June 4, 2024 at 11:27:39 AM UTC-5 Joyner Library wrote:
> Hi All,
>
> We have enabled sword version 1 in the local configuration but haven't 
> changed other sword settings. I can sign on to the frontend and /server too. 
> When we try to download https://irdev.ecu.edu/server/sword/servicedocument it 
> gives the white label error page. The DSpace log file shows:
>
> INFO unknown 4f89ae89-9baf-49cc-b800-3205dbddef5d 
> org.dspace.authenticate.LDAPAuthentication @ 
> anonymous:session_id=0:ip_addr=150.216.*.*:auth:attempting trivial auth of 
> user=crimin
>
> 2024-06-04 12:00:32,819 ERROR unknown unknown 
> org.springframework.boot.web.servlet.support.ErrorPageFilter @ Forwarding to 
> error page from request [/sword/servicedocument] due to exception 
> [java.lang.NullPointerException: Cannot invoke 
> "javax.servlet.http.HttpServletRequest.setAttribute(String, Object)" because 
> "request" is null]
>
> How do I sign on successfully to the sword service?
>
> Nick Crimi
> ECU Libraries

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
library.indianapolis.iu.edu
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/3c7d1871-42b6-4f9c-82b3-ede1bff3a393n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB108152D8F575491EC3E89D743E8C72%40YT3PR01MB10815.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Re: Issue with Author Indexing in DSpace 7

[Sean Kalynuk]

I might be able to help with this one. My notes suggest this was a DSpace 7.4 
issue where authority keys would be shown in the Author Browse list for 
non-discoverable/withdrawn items. I seem to recall that updates with the 
internal discovery mechanism resolved the issue in DSpace 7.5. So I’d suggest 
upgrading to at least version 7.5 (if you are not there yet), and/or re-running 
index-authority. We are running DSpace 7.5 and I have not seen this issue since 
we upgraded.

--
Sean

From: DSpace Technical Support 
Date: Friday, June 7, 2024 at 3:37 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: Issue with Author Indexing in DSpace 7
Caution! This message was sent from outside the University of Manitoba.

Hi Humberto,

It's difficult for anyone to help without more information.  What version of 
DSpace 7 are you using?  Are these "authors" you are referencing Author 
*entities* or just Author strings?  Are you using DSpace's Authority Control 
feature?

>From the screenshot you've shared & the details in your email, it's very 
>difficult to determine what the issue may be.  It's possible this is an other 
>bug that's been fixed in a more recent version of 7.x.  Or, it could be a new 
>bug that we're unaware of.

You also may want to verify whether you see the same behavior on our demo site 
(https://demo.dspace.org) as that can verify whether or not this is a bug in 
DSpace.

Tim
On Tuesday, June 4, 2024 at 12:36:57 AM UTC-5 hbla...@gmail.com wrote:



Hello everyone,

I hope you are all well.

I am encountering a problem in our DSpace repository that I hope you can help 
me resolve. Upon reviewing the author indexing, I have noticed that some 
identifiers are not being indexed correctly, which is affecting the visibility 
and accessibility of the documents in our repository.

Attached is an image with some examples of these identifiers:

The specific problem I am observing is as follows:

  *   Incorrectly indexed author identifiers: Instead of displaying the names 
of the authors, alphanumeric identifiers are being shown.
  *   Impact on visibility: This affects the search and retrieval of documents 
by end users, as they cannot search directly by author names.

Any guidance on how to resolve this issue would be greatly appreciated. If 
anyone has faced a similar problem or has any suggestions on possible 
solutions, I would greatly appreciate your help.

Thank you very much in advance for your time and support.



Humberto
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/e10d1a1f-2010-49d6-a62e-fdc9e4d22f95n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB1081596713A5AEB0B447D2708E8FB2%40YT3PR01MB10815.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Automatic start front end at boot

[Sean Kalynuk]

Hi Joshua,

You can follow the instructions here:

https://pm2.keymetrics.io/docs/usage/startup/

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Joshua Kim 
Date: Monday, January 8, 2024 at 3:15 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Automatic start front end at boot
Caution: This message was sent from outside the University of Manitoba.

Hello,

Does anyone use automatic start of dspace front end at reboot by using service 
? If so, would you share with us? The 7.x documentation shows only manual start 
like pm2 start dspace-ui.json.

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/76456ab7-2415-436e-9694-905830e84569n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB81477611EB9A2909B2C71CC4E86B2%40YT3PR01MB8147.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Re: Integrate ORCID to DSpace 7 authentication

[Sean Kalynuk]

Hi Andrew,

The public API URL is:

https://pub.orcid.org/v3.0

The https://api.orcid.org/v3.0 URL is the Member API.

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Andrew K 
Date: Sunday, December 3, 2023 at 2:46 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: Integrate ORCID to DSpace 7 authentication
Caution: This message was sent from outside the University of Manitoba.

dspace log has nothing about it
tomcat log has this for every authentification attempt
127.0.0.1 - - [03/Dec/2023:10:05:29 +0200] "GET 
/server/api/authn/orcid?code=KNOI5s HTTP/1.1" 302 -

субота, 2 грудня 2023 р. о 20:49:40 UTC+2 Andrew K пише:
Probably worth metnioning that the return URL in browser is 
https://my.dspace.website/error?status=401&code=orcid.generic-error
I.e., that might be another error not related to the account email address.

And I use public API key.

субота, 2 грудня 2023 р. о 20:20:00 UTC+2 Andrew K пише:
Hey guys!

I'm having exactly the same problem in 7.6

401unauthorized
An error occurred during login via ORCID. Make sure you have shared your ORCID 
account email address with DSpace. If the error persists, contact the 
administrator

My orcid.cfg :

#--#
#ORCID GENERIC CONFIGURATIONS--#
#--#
# Configuration with which it is established which user can disconnect a 
profile from orcid (none, only the admin, only the owner or both).
# Allowed values are disabled, only_admin, only_owner or admin_and_owner
orcid.disconnection.allowed-users = admin_and_owner
#--#
#ORCID CLIENT CONFIGURATIONS---#
#--#
# ORCID API 
(https://github.com/ORCID/ORCID-Source/tree/master/orcid-api-web#endpoints)
#orcid.domain-url= https://sandbox.orcid.org
orcid.domain-url= https://orcid.org
orcid.authorize-url = ${orcid.domain-url}/oauth/authorize
orcid.token-url = ${orcid.domain-url}/oauth/token
orcid.api-url = https://api.orcid.org/v3.0
orcid.public-url = https://pub.orcid.org/v3.0
orcid.redirect-url = ${dspace.server.url}/api/authn/orcid

# ORCID Credentials
# Your public or member API Credentials, see
# https://orcid.org/content/register-client-application-0
# https://info.orcid.org/register-a-client-application-sandbox-member-api/
orcid.application-client-id = APP-
orcid.application-client-secret = x-x-xxx-xx

# The scopes to be granted by the user during the login on ORCID (see 
https://info.orcid.org/faq/what-is-an-oauth-scope-and-which-scopes-does-orcid-support/)
orcid.scope = /authenticate
#orcid.scope = /read-limited
#orcid.scope = /activities/update
#orcid.scope = /person/update

I also tried setting email visible to Everyone.
Interesting that I see in ORCID trusted parties Access type: Get your ORCID iD 
while other trusted parties might have Access type: Read your information with 
visibility set to Trusted Parties.

I.e. that looks like DSpace doesn't even ask for the email, right?

WBR,
Andrew

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/ad35b2a1-8146-47f0-95b8-f38ce33bf0a8n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB814779AB670FF192A1DF9172E885A%40YT3PR01MB8147.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Upgraded Maven required for 7.6.1?

[Sean Kalynuk]

Hi Hrafn,

I agree that it is best to just upgrade the documented requirements.

--
Sean

From: Hrafn Malmquist 
Date: Friday, November 24, 2023 at 8:00 AM
To: Sean Kalynuk 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] Upgraded Maven required for 7.6.1?
Caution: This message was sent from outside the University of Manitoba.

Hi Sean

Thanks for pointing this out. This is due to my PR 
https://github.com/DSpace/DSpace/pull/9016 that bumped up the 
buildnumber-maven-plugin version from 1.4 => 3.2.0. see 
https://github.com/DSpace/DSpace/pull/9016

I did not realise this would up the required Maven version as listed in the 
docs. It's not easy to gather release history from the documentation on the 
plugin's website: https://www.mojohaus.org/buildnumber-maven-plugin/. However 
in the plugin's Github it does say that Maven 3.5.4 is required starting with 
version 3.1.0 (https://github.com/mojohaus/buildnumber-maven-plugin/releases).

We have the option to either revert to plugin version 3.0.0 or up the doc 
requirements to indicate Maven 3.5.4 is required. I lean towards the latter 
option.

Best regards, Hrafn

On Thu, Nov 23, 2023 at 4:36 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
It looks like there is now a higher version requirement for Maven?

Docs say 3.3.x+ (as of today):

https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-ApacheMaven3.3.xorabove(Javabuildtool)

There is mention of using 3.8.x and 3.6.x though.

A “mvn package” (using Maven 3.3.9) on 7.6.1 server recently produced this 
error:

“Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:3.2.0:create 
(default) on project dspace-api: The plugin 
org.codehaus.mojo:buildnumber-maven-plugin:3.2.0 requires Maven version 3.5.4”

--
Sean
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB81471D4CC41E58B47E944C25E8B9A%40YT3PR01MB8147.CANPRD01.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB81471D4CC41E58B47E944C25E8B9A%40YT3PR01MB8147.CANPRD01.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer>.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB814722DA1E8D6C3917953BA3E8B8A%40YT3PR01MB8147.CANPRD01.PROD.OUTLOOK.COM.

[dspace-tech] Upgraded Maven required for 7.6.1?

[Sean Kalynuk]

It looks like there is now a higher version requirement for Maven?

Docs say 3.3.x+ (as of today):

https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-ApacheMaven3.3.xorabove(Javabuildtool)

There is mention of using 3.8.x and 3.6.x though.

A “mvn package” (using Maven 3.3.9) on 7.6.1 server recently produced this 
error:

“Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:3.2.0:create 
(default) on project dspace-api: The plugin 
org.codehaus.mojo:buildnumber-maven-plugin:3.2.0 requires Maven version 3.5.4”

--
Sean

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB81471D4CC41E58B47E944C25E8B9A%40YT3PR01MB8147.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] PM2 uses a lot of memory and causes automatic Solr shutdown.

[Sean Kalynuk]

In our DSpace 7.5 environment (RHEL7, 16GB, 8 CPUs), I chose to only use 4 CPUs 
out of 8 ("instances": "4") for Node since we also run the other processes 
(Tomcat9 and Solr) on the same VM. The default Node 16 heap size is 2GB 
(verified with node -p 'v8.getHeapStatistics()'), and, originally, we were 
running into Node core dumps due to out-of-memory exceptions. At that time, I 
set "max_memory_restart": "1800M" so that the Node processes would be restarted 
before a core dump. However, after enabling server-side caching, the memory 
core dumps stopped and our Node process runtimes (before restart) changed from 
roughly 45 minutes to many days.
--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Javi Rojo Díaz 
Date: Monday, October 23, 2023 at 3:34 AM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] PM2 uses a lot of memory and causes automatic Solr 
shutdown.
Caution: This message was sent from outside the University of Manitoba.


Thank you very much for your response!

For now, what I've done is to limit the memory usage for each core/node of PM2 
cluster to 500MB. So, if I have 8 nodes in the cluster, the maximum memory used 
by PM2 should be 500MB x 8 nodes = 5GB RAM. This seems like a reasonable memory 
usage. Since I restarted PM2, the memory usage has significantly decreased, and 
so far, no node has reached 500MB to see if it automatically restarts.

I'll continue monitoring it, but it appears that this may be the solution.

To limit memory usage, I added the following line to "dspace-ui.json":

"max_memory_restart": "500M"

[cid:3eefe9be-cebf-4db3-a95c-d06f94da560a]

 And I restarted PM2 to apply it. I'll write here again if this adjustment has 
indeed resolved the issue.

 Thanks for everything!
El lunes, 23 de octubre de 2023 a las 9:58:00 UTC+2, dataquest escribió:
Hello. I am not sure if I am the best one to answer this question, but we 
encountered similar problem.
We thought majority of the memory was spent for caching purposes.
Therefore we decreased caching significantly, I can look up specific numbers 
later, but it was
at most in hundreds. It is much less than official documentation recommends.
I also used this parameter in dspace-ui.json that is used to start pm2.
"node_args": "--max_old_space_size=4096"

I noticed that even if this memory is insufficient, one core crashes, pm2 
restarts it
and after that all works well. It is certainly not a good behaviour and if you 
use that
parameter, beware of this possibility and monitor the cores for a while. If 
they keep
restarting, they don't have enough memory and something should be done.

Hope this helps, but perhaps someone else will have some better advice.

Majo

On Mon, Oct 23, 2023 at 9:50 AM Javi Rojo Díaz  wrote:
Good morning,

We have Dspace 7.5 installed and running in production on a machine with 16GB 
of RAM. For some time now, we have been noticing high RAM usage on the machine. 
It appears that PM2 is consuming the majority of the system's memory. It's 
currently using 11GB of RAM, as you can see in the screenshot:

[cid:~WRD0001.jpg]

[cid:~WRD0001.jpg]

This high memory usage is causing our Solr service to stop every night when it 
tries to perform the scheduled reindexing. Could you please advise us on how to 
resolve this issue so that PM2 doesn't use so much memory and leave other 
services inoperable?


Thank you very much for your assistance.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/7829c1f2-86ff-46fb-a423-4b7a88cacab6n%40googlegroups.com.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/3f64ad60-c5af-4198-8430-c67bff896974n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical S

Re: [dspace-tech] Embargo date can't be more than 3 years in the future?

[Sean Kalynuk]

Hi Paige,

The relevant documentation you are looking for can be found here:

https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface#SubmissionUserInterface-Modifyingaccessconditions(embargo,etc.)presentedforBitstreams

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Paige Morgan 
Date: Wednesday, September 20, 2023 at 11:03 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Embargo date can't be more than 3 years in the future?
Caution: This message was sent from outside the University of Manitoba.

Hi, all--

We're running DSpace 7.4, and we recently ran into an issue when trying to set 
an embargo for an open-access version of a scholarly publication. The 
publication has a 48-month embargo, but the interface won't let us set an 
embargo date that is later than September 2026 (36 months).

I thought this might be a local setting for us, but I found the same limit in 
the demo.dspace.org sandbox -- though I'm not finding 
any indication in the 
documentation that the 
36-month limit is intentional. Is this a hard limit, or just a configuration 
setting that we need to change?

Thanks in advance!
Paige

-
Meeting/regular work hours: Monday - Friday, 9am-4:30pm


Dr. Paige C. Morgan
(she/they)
Digital Publishing and Copyright Librarian,
Head of Digital Initiatives & Preservation
University of Delaware Library, Museums and Press (on Lenape 
land)
Morris 118
ORCID: https://orcid.org/-0001-8076-7356
paig...@udel.edu
302.831.7153

Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings 
available via Zoom, phone, etc.)
** I observe email-free evenings and weekends. **

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVdkE-JXOacdoJh-JnkFjgneOq00MfYgEb%2BxvLsrojLG6fw%40mail.gmail.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YQBPR01MB10515B89516E9807928265705E8F9A%40YQBPR01MB10515.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Problem with controlled vocabularies in submission forms and the browse dropdown

[Sean Kalynuk]

Hi Donna,

I think it is this issue:

https://github.com/DSpace/DSpace/issues/8927

--
Sean

From: 'donna@canterbury.ac.nz' via DSpace Technical Support 

Date: Sunday, July 23, 2023 at 8:10 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Problem with controlled vocabularies in submission forms 
and the browse dropdown
Caution: This message was sent from outside the University of Manitoba.


We’re trying to upgrade from 6.3 to 7.6, and we’re encountering a problem with 
the browse dropdown disappearing from the navbar when we configure controlled 
vocabularies in submission-forms.xml. Is this something anyone else has 
experienced and know what the cause could be?

We’ve tried adding the default srsc vocabulary to our submission form to see if 
our customised vocabs were the cause, but the same thing happens. I can’t see 
anything useful in the logs or browser tools.

Many thanks for any help,
Donna
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/c4bb7a0a-0990-48f9-80f2-ded3ab8d8882n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YQBPR01MB105155DBA5BD9FC54DB3EE696E802A%40YQBPR01MB10515.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Re: Dspace 7.5 performace

[Sean Kalynuk]

In addition to the performance improvements, enabling server-side caching has 
also resolved a possible memory leak issue we were experiencing. With PM2 
managing Node, and using max_memory_restart, the Node processes would restart 
about every hour or so. Now everything is stable.

For reference, we are using:

DSpace 7.5
Node v16.18.1
RHEL 7.9

botCache and anonymousCache max were set low at 100 for now just to try things 
out.

--
Sean

From: DSpace Technical Support 
Date: Thursday, July 13, 2023 at 3:29 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: Dspace 7.5 performace
Caution: This message was sent from outside the University of Manitoba.

I'd also recommend that anyone using DSpace 7.5 consider enabling the new 
"caching of server-side rendered pages" feature for anonymous users:

https://wiki.lyrasis.org/display/DSDOC7x/Performance+Tuning+DSpace#PerformanceTuningDSpace-Turnon(orincrease)cachingofServer-SideRenderedpages

Simply put, one of the areas where a site can see slowness (especially to the 
homepage) is during "server-side rendering".  Each time a user visits your 
site, the *first* page they receive is flat HTML (which is dynamically built 
via server-side rendering).  This is a feature of Angular which tries to speed 
up the initial page by sending immediate HTML while the Javascript app is still 
downloading... once the Javascript app finishes, it replaces the flat HTML and 
allows you to interact with the page.

However, on very complex pages or pages with a lot of content (like the 
homepage) , the server-side rendering can take time/resources to generate that 
flat HTML *on demand*.   That's why we've added the caching feature to cache 
these flat HTML pages for anonymous usersit ensures that the server-side 
rendering runs *less frequently*, and the same flat HTML page can be cached & 
returned for many anonymous users.  That said, this caching is disabled by 
default at this time.

We've enabled this caching on https://demo7.dspace.org/ to allow the homepage 
to load more rapidly.

Take a look at the docs here for more information: 
https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Configuration#UserInterfaceConfiguration-CacheSettings-ServerSideRendering(SSR)

Tim


On Wednesday, July 12, 2023 at 1:55:03 AM UTC-5 tif...@gmail.com wrote:
Hi,

Are you sure your frontend works in cluster mode?
This issue was recently discussed here:
https://groups.google.com/g/dspace-tech/c/dSHHObckkIc/m/jztWqQpTAwAJ

Regards,
Mariusz

wtorek, 11 lipca 2023 o 14:38:14 UTC+2 Edmund Balnaves napisał(a):
I don't know how your proxy is wired up, but I got a benefit from binding the 
external host name in /etc/hosts to the internal IP - that kept a lot API 
traffic from hitting the external interface.

The home page generates a lot of API calls.   On my server the ratio is 1 page 
: 10 API calls overall.

I will be interested to see any ideas on this question.


On Tuesday, July 11, 2023 at 7:55:57 PM UTC+10 emilio lorenzo wrote:
Hello,

Is there any recomendation to improve the initial load time of Dspace 7
home page ?  We are suffering high load times ( and consistent) at a
production site.   (Lots an lots of cpu and memory available)

The recommendations of
https://wiki.lyrasis.org/display/DSDOC7x/Performance+Tuning+DSpace has
been applied and we have alredy  paid attention to this thread:
https://www.mail-archive.com/dspac...@googlegroups.com/msg14510.html

We wonder if anyone has additional tips. We are running low in ideas.

Thanks



--
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/db51e722-e5bd-4853-b059-925c824b4265n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT2PR01MB1052406667E438CE7F46B73C2E834A%40YT2PR01MB10524.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] OAI-PMH returns http URLs in the metadata field

[Sean Kalynuk]

Hi Bryan,

In your local.cfg file (or dspace.cfg), the Handle prefix is configured with:

handle.canonical.prefix

Note that changing this configuration parameter will not change any existing 
dc.identifier.uri metadata (where the Handle is stored). It would only apply to 
newly archived items.

The OAI bitstream URL prefix can be configured with:

oai.bitstream.baseUrl

When changing this parameter, you will need to run “dspace oai import -c” to 
re-create the stored XML used by OAI when applying crosswalks.

After that, make sure you run “dspace oai clean-cache” to make sure you don’t 
get any stale data from before.

As for when you say “The URLs in DB are HTTPS” I’m not sure what might be going 
there, unless maybe you have a crosswalk rule that is changing them.

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Snickers 
Date: Monday, June 19, 2023 at 10:34 PM
To: DSpace Technical Support 
Subject: [dspace-tech] OAI-PMH returns http URLs in the metadata field
Caution: This message was sent from outside the University of Manitoba.

Hi All,

We use Dspace 7.4 and OAI-PMH works well.

The issue is that the URLs for handle.net and bitstream download show HTTP 
instead of HTTPS. How can we convert the URLs provided by OAI-PMH to be HTTPS?

The URLs in DB are HTTPS so not sure why the metadata provides HTTP URLs.

Regards,
Bryan
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/79497055-9c41-4d05-ac44-6bec1666eb89n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YQBPR01MB10515F6F26EEC49D5F0B3B7C1E85CA%40YQBPR01MB10515.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] DSpace 7 - Browse by Author not showing name but showing UUID

[Sean Kalynuk]

I have seen this before. What exact version of DSpace 7.x are you using?

I would suggest trying to rebuild the Solr search core first with “dspace 
index-discovery -b”.

With versions of DSpace 7.x before 7.5, I was seeing authority keys instead of 
author names for items that were withdrawn. When in as Administrator, I was 
also seeing authors as authority keys for non-discoverable items as well.

It may have been due to this issue that was fixed in 7.4: 
https://github.com/DSpace/DSpace/issues/8479

I have not seen the issue with 7.5 yet.

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
hb wooley 
Date: Wednesday, April 5, 2023 at 3:51 PM
To: DSpace Technical Support 
Subject: [dspace-tech] DSpace 7 - Browse by Author not showing name but showing 
UUID
Caution: This message was sent from outside the University of Manitoba.

I've been working on migrating from DSpace 6 using Oracle to DSpace 7 using 
Postgres and believe I have been able to transfer the data properly. However, 
when I go to "Browse by Author" some of the records show a UUID, 
dspace_object_id, resource_id, or authority when I should be seeing the Authors 
name. Example:
Name  ( record_count ) -- the below are links
==
Curts, Bob (1)
Cutters, Phill  (1)
Cutlers, Tom.(1)
Franks, Martin T.(12)
Damato, C. (14)
d002dfcc-1eb9-4dad-a018-11a3513cab55 (2)
d0046ab5-84ea-464e-a025-cb10a61ca2ff (13)
d00cc826-77cb-448b-9efd-e4f0ad7519cd (11)
d013e0bc-44cc-495d-be49-d7b66fd74af4 (19)

The our Dspace 6.x is working properly. Can someone point me to where I can 
resolve this issue?

Thanks in advance!

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/10fe6866-c77a-4693-a184-af350337827an%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YQBPR01MB1051598B465EBC2EBF959C7D9E8919%40YQBPR01MB10515.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] ORCID autohority in DSpac 7.5

[Sean Kalynuk]

Hi Milos,

I think it is this bug:

https://github.com/DSpace/dspace-angular/issues/1758

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Milos Ivanovic 
Date: Sunday, March 19, 2023 at 3:11 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] ORCID autohority in DSpac 7.5
Caution: This message was sent from outside the University of Manitoba.

Dear Sean,

I've forgotten to comment on one more issue. When submitting a new item, one 
gets suggestions from ORCID API on i.e. dc.contributor.author fields. However, 
when editing items, the suggestions are missing. If one types the surname and 
first name of the author, that author just gets overwritten in Solr, getting a 
new authority ID. Is this a bug or a feature? Is there an option to force those 
fields to behave the way when submitting a new item?

Regards
Milos

среда, 8. март 2023. у 21:40:54 UTC+1 Milos Ivanovic је написао/ла:
Dear Sean,

Many thanks for your thorough explanation. IMHO the improvement in this respect 
is worth considering.

Regards
Milos

среда, 8. март 2023. у 01:04:30 UTC+1 Sean Kalynuk је написао/ла:
Hi Milos,

After looking through the DSpace 7.5 code, I don’t see that institution can be 
configured to be displayed in the search results. (Although, there are bits and 
pieces in the code that seem to indicate that it’s not that far away from being 
supported.)

The author search display results are limited to:

last-name
first-name
orcid
insolr (this is an indicator if the result came from the authority Solr core, 
and would have a UUID if so, otherwise, it will say “false” in which case the 
result came from the ORCID API)

However, there are other ORCID Person values obtained during the search, 
including:

  *   Keywords
  *   External identifiers
  *   Researcher URLs
  *   Biography

You can see what the ORCID API returns for a Person here:
https://github.com/ORCID/orcid-model/blob/master/src/main/resources/record_3.0/person-3.0.xsd

None of these other values are made available for display in the search results 
though. However, they are stored in the Solr authority core so could 
potentially be used at some point.

Surprisingly, there is an internal “institution” value that could also 
potentially be used, but there is no current mapping from the ORCID Person 
record to an institution value that DSpace could use for display purposes.

I figure it’s important to point out that there are several other quirks with 
the implementation that cause some difficulty in finding ORCID authors. For 
example, the ORCID API result list is hard-coded to at most 10 results. Also, 
the ORCID API search is so generic that searching for first name and last name 
(instead of just last name) can result in not being able to even find the 
person you’re looking for (if outside the 10 results limit). I find better 
results when only using last name in the search. (Of course, it all depends on 
how unique the last name is.)

Perhaps the future lies with ORCID Person entities and not the ORCID Authority 
implementation?

--
Sean

From: dspac...@googlegroups.com  on behalf of Milos 
Ivanovic 
Date: Tuesday, March 7, 2023 at 11:51 AM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] ORCID autohority in DSpac 7.5
Caution: This message was sent from outside the University of Manitoba.

Perfect. Thanks, @Sean, it really works with the public API! This is something 
I've been looking for. Will give it a more thorough test.

One more quick question if anyone knows. Do you know how to add the name of the 
institution from the ORCID profile to the suggestions? It would make the 
process much easier IMHO.

Kind regards!
Milos

уторак, 7. март 2023. у 18:35:17 UTC+1 darryl@usask.ca је написао/ла:
(sorry, hit the post button too soon)

I'm now seeing the same error in the logs you noted in  8436 
https://github.com/DSpace/DSpace/issues/8436#issuecomment-1249577192

While I'm a little bummed the ORCID stuff is still not quite there yet, its at 
least reassuring to know that my setup is working as well as can be expected 
right now.

Thanks again!

- Darryl
On Tuesday, March 7, 2023 at 11:27:16 AM UTC-6 darryl@usask.ca wrote:
Thanks Sean.  With the sections of orcid-authority-services.xml uncommented, 
and a correction to a typo in my local.cfg I'm now seeing results back from the 
ORCID API. Like you, I'm using the public URLs for both orcid.api-url and 
orcid.public-url.
On Tuesday, March 7, 2023 at 10:31:59 AM UTC-6 Sean Kalynuk wrote:
Hi Darryl and Milos,

You do need to uncomment the proper sections in orcid-authority-services.xml. I 
had the same “No bean named ‘AuthoritySource’ available” error until I modified 
the configuration. The relevant comment is the one I made here:
https://github.com/DSpace/DSpace/issues/8436#issuecomment-1248565724

However, Milos, I compared your orcid-authority-services.xml to mine and they 
are identical (ignoring whitespace).

One difference I did notice in the

Re: [dspace-tech] ORCID autohority in DSpac 7.5

[Sean Kalynuk]

Hi Milos,

After looking through the DSpace 7.5 code, I don’t see that institution can be 
configured to be displayed in the search results. (Although, there are bits and 
pieces in the code that seem to indicate that it’s not that far away from being 
supported.)

The author search display results are limited to:

last-name
first-name
orcid
insolr (this is an indicator if the result came from the authority Solr core, 
and would have a UUID if so, otherwise, it will say “false” in which case the 
result came from the ORCID API)

However, there are other ORCID Person values obtained during the search, 
including:

  *   Keywords
  *   External identifiers
  *   Researcher URLs
  *   Biography

You can see what the ORCID API returns for a Person here:
https://github.com/ORCID/orcid-model/blob/master/src/main/resources/record_3.0/person-3.0.xsd

None of these other values are made available for display in the search results 
though. However, they are stored in the Solr authority core so could 
potentially be used at some point.

Surprisingly, there is an internal “institution” value that could also 
potentially be used, but there is no current mapping from the ORCID Person 
record to an institution value that DSpace could use for display purposes.

I figure it’s important to point out that there are several other quirks with 
the implementation that cause some difficulty in finding ORCID authors. For 
example, the ORCID API result list is hard-coded to at most 10 results. Also, 
the ORCID API search is so generic that searching for first name and last name 
(instead of just last name) can result in not being able to even find the 
person you’re looking for (if outside the 10 results limit). I find better 
results when only using last name in the search. (Of course, it all depends on 
how unique the last name is.)

Perhaps the future lies with ORCID Person entities and not the ORCID Authority 
implementation?

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Milos Ivanovic 
Date: Tuesday, March 7, 2023 at 11:51 AM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] ORCID autohority in DSpac 7.5
Caution: This message was sent from outside the University of Manitoba.

Perfect. Thanks, @Sean, it really works with the public API! This is something 
I've been looking for. Will give it a more thorough test.

One more quick question if anyone knows. Do you know how to add the name of the 
institution from the ORCID profile to the suggestions? It would make the 
process much easier IMHO.

Kind regards!
Milos

уторак, 7. март 2023. у 18:35:17 UTC+1 darryl@usask.ca је написао/ла:
(sorry, hit the post button too soon)

I'm now seeing the same error in the logs you noted in  8436 
https://github.com/DSpace/DSpace/issues/8436#issuecomment-1249577192

While I'm a little bummed the ORCID stuff is still not quite there yet, its at 
least reassuring to know that my setup is working as well as can be expected 
right now.

Thanks again!

- Darryl
On Tuesday, March 7, 2023 at 11:27:16 AM UTC-6 darryl@usask.ca wrote:
Thanks Sean.  With the sections of orcid-authority-services.xml uncommented, 
and a correction to a typo in my local.cfg I'm now seeing results back from the 
ORCID API. Like you, I'm using the public URLs for both orcid.api-url and 
orcid.public-url.
On Tuesday, March 7, 2023 at 10:31:59 AM UTC-6 Sean Kalynuk wrote:
Hi Darryl and Milos,

You do need to uncomment the proper sections in orcid-authority-services.xml. I 
had the same “No bean named ‘AuthoritySource’ available” error until I modified 
the configuration. The relevant comment is the one I made here:
https://github.com/DSpace/DSpace/issues/8436#issuecomment-1248565724

However, Milos, I compared your orcid-authority-services.xml to mine and they 
are identical (ignoring whitespace).

One difference I did notice in the config is that I am using the public ORCID 
API for testing:

orcid.api-url = https://pub.orcid.org/v3.0

whereas you are using the member API:

orcid.api-url = https://api.orcid.org/v3.0

I have not configured full ORCID integration yet, and am only using the public 
API for author lookup. Perhaps you could try with the public API just for 
author lookup to see if that would work first? I have been using the developer 
credentials for my personal ORCID account for testing and it has connected and 
found ORCID records while searching for a dc.contributor.author value in a 
submission form.

One thing to point out though is that there is an outstanding bug with the 
“will be generated” authority keys related to ORCID authority records:

https://github.com/DSpace/DSpace/issues/8490

This occurs with newly found ORCID records from the ORCID API (not those in 
your authority Solr core) since they need to have authority keys generated.

--
Sean

From: dspac...@googlegroups.com  on behalf of 
darryl@usask.ca 
Date: Monday, March 6, 2023 at 5:35 PM
To: DSpace Technical Support 
Subject: Re: [dspace-

Re: [dspace-tech] ORCID autohority in DSpac 7.5

[Sean Kalynuk]

Hi Darryl and Milos,

You do need to uncomment the proper sections in orcid-authority-services.xml. I 
had the same “No bean named ‘AuthoritySource’ available” error until I modified 
the configuration. The relevant comment is the one I made here:
https://github.com/DSpace/DSpace/issues/8436#issuecomment-1248565724

However, Milos, I compared your orcid-authority-services.xml to mine and they 
are identical (ignoring whitespace).

One difference I did notice in the config is that I am using the public ORCID 
API for testing:

orcid.api-url = https://pub.orcid.org/v3.0

whereas you are using the member API:

orcid.api-url = https://api.orcid.org/v3.0

I have not configured full ORCID integration yet, and am only using the public 
API for author lookup. Perhaps you could try with the public API just for 
author lookup to see if that would work first? I have been using the developer 
credentials for my personal ORCID account for testing and it has connected and 
found ORCID records while searching for a dc.contributor.author value in a 
submission form.

One thing to point out though is that there is an outstanding bug with the 
“will be generated” authority keys related to ORCID authority records:

https://github.com/DSpace/DSpace/issues/8490

This occurs with newly found ORCID records from the ORCID API (not those in 
your authority Solr core) since they need to have authority keys generated.

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
darryl@usask.ca 
Date: Monday, March 6, 2023 at 5:35 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] ORCID autohority in DSpac 7.5
Caution: This message was sent from outside the University of Manitoba.

Milos, do you see anything in your logs/dspace.log file related to ORCID?  I 
can't seem to get the ORCID lookup working either.  I've double and triple 
checked all my config and I can't find any issues.  However, in my DSpace logs 
I see the same "No bean named 'AuthoritySource' available" and " 
org.dspace.content.authority.SolrAuthority @ external source for authority not 
configured" warnings mentioned in issue 8436 -- 
https://github.com/DSpace/DSpace/issues/8436 and I'm curious if that is showing 
up for you as well.

There's a comment in that issue that mentions uncommenting some code in 
dspace/config/spring/api/orcid-authority-services.xml which I haven't looked 
into yet.  I also see that this issue was moved to the DSpace 7.6 To-Do list by 
Tim Donohue.  I wondering if maybe the ORCID lookup stuff is still not quite 
ready for production usage?

- Darryl



On Monday, March 6, 2023 at 7:12:03 AM UTC-6 Milos Ivanovic wrote:
Besides author lookup using ORCID (which is my primary use case), in order to 
check the communication with ORCID API, I also tried to configure ORCID 
authentication. No luck. The ORCID account has a publicly visible email, bound 
to the DSpace account, my site is HTTPS enabled, but it's still not working :(

Can anyone send me an anonymized working config or any other advice on what to 
check? Thanks in advance.

Kind regards
Milos

петак, 3. март 2023. у 17:34:24 UTC+1 Milos Ivanovic је написао/ла:
Sorry, I have forgotten to mention it. This setting is ok too.


петак, 3. март 2023. у 16:46:43 UTC+1 Sean Kalynuk је написао/ла:
Hi Milos,

Do you also have:

plugin.named.org.dspace.content.authority.ChoiceAuthority = \
  org.dspace.content.authority.SolrAuthority = SolrAuthorAuthority

I don’t see it in your config (at least in this message).

It is commented out by default in 
[your-dspace-home]/config/modules/authority.cfg

--
Sean

From: dspac...@googlegroups.com  on behalf of Milos 
Ivanovic 
Date: Friday, March 3, 2023 at 4:17 AM
To: DSpace Technical Support 
Subject: [dspace-tech] ORCID autohority in DSpac 7.5
Caution: This message was sent from outside the University of Manitoba.

Dear All,

I am trying to enable ORCID authority according to 
https://wiki.lyrasis.org/display/DSDOC7x/ORCID+Authority. However,  the 
suggestions from the ORCID API do not appear in the  Author field of the 
"Submit new item" component. The relevant part of local.cfg looks like this:

choices.plugin.dc.contributor.author = SolrAuthorAuthority
choices.presentation.dc.contributor.author = authorLookup
authority.controlled.dc.contributor.author = true
authority.author.indexer.field.1=dc.contributor.author
auto-update-items = true
event.dispatcher.default.consumers = authority, versioning, discovery, eperson
orcid.domain-url= https://orcid.org
orcid.api-url = https://api.orcid.org/v3.0
orcid.public-url = https://pub.orcid.org/v3.0
orcid.application-client-id = APP-
orcid.application-client-secret = 

The API is normally enabled in my ORCID profile. Also, 
orcid-authority-services.xml is attached. There are no traces of erroneous (or 
any other) ORCID API requests in DSpace and Tomcat logs.

Am I missing something obvious?

Th

Re: [dspace-tech] ORCID autohority in DSpac 7.5

[Sean Kalynuk]

Hi Milos,

Do you also have:

plugin.named.org.dspace.content.authority.ChoiceAuthority = \
  org.dspace.content.authority.SolrAuthority = SolrAuthorAuthority

I don’t see it in your config (at least in this message).

It is commented out by default in 
[your-dspace-home]/config/modules/authority.cfg

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Milos Ivanovic 
Date: Friday, March 3, 2023 at 4:17 AM
To: DSpace Technical Support 
Subject: [dspace-tech] ORCID autohority in DSpac 7.5
Caution: This message was sent from outside the University of Manitoba.

Dear All,

I am trying to enable ORCID authority according to 
https://wiki.lyrasis.org/display/DSDOC7x/ORCID+Authority. However,  the 
suggestions from the ORCID API do not appear in the  Author field of the 
"Submit new item" component. The relevant part of local.cfg looks like this:

choices.plugin.dc.contributor.author = SolrAuthorAuthority
choices.presentation.dc.contributor.author = authorLookup
authority.controlled.dc.contributor.author = true
authority.author.indexer.field.1=dc.contributor.author
auto-update-items = true
event.dispatcher.default.consumers = authority, versioning, discovery, eperson
orcid.domain-url= https://orcid.org
orcid.api-url = https://api.orcid.org/v3.0
orcid.public-url = https://pub.orcid.org/v3.0
orcid.application-client-id = APP-
orcid.application-client-secret = 

The API is normally enabled in my ORCID profile. Also, 
orcid-authority-services.xml is attached. There are no traces of erroneous (or 
any other) ORCID API requests in DSpace and Tomcat logs.

Am I missing something obvious?

Thanks in advance
Milos
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/588f9cbd-cb46-4738-9794-8f2fad2deb37n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB816487FA12B993552C99F98BE8B39%40YT3PR01MB8164.CANPRD01.PROD.OUTLOOK.COM.

[dspace-tech] Question about reporting 7.x documentation issues

[Sean Kalynuk]

What is the standard procedure for reporting 7.x documentation errors?

Are they reported as “bugs” at:

https://github.com/DSpace/DSpace/issues/new/choose

Thanks!

--
Sean

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB81647980245377EDD88DCA7FE8729%40YT3PR01MB8164.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Re: ORCID intergration displays ID in Browse by Author

[Sean Kalynuk]

This appears to be fixed in DSpace 6.4:

https://github.com/DSpace/DSpace/issues/6208

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Usv 
Date: Wednesday, July 20, 2022 at 6:53 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: ORCID intergration displays ID in Browse by Author
Caution: This message was sent from outside the University of Manitoba.

Hi,

Is there a solution to this problem?
I have the same problem in dspace 6.3 with ORCID enabled. In Browse by author 
list appears key instead of author's name.
Thanks a lot.
Pe vineri, 28 mai 2021, la 12:16:25 UTC+3, John S. a scris:

In a dspace 6.3 installation with the ORCID Integration enabled, the authors 
who are lookuped and matched with an ORCID ID, are not displayed in the Browse 
by Author list with their names but rather with their ORCID ids (see attached 
fig).
Any ideas concerning the missing/ wrong configuration?

Thanks in advance

John
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/fb0d14a3-6e5b-430c-8556-4beb8c8384aen%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB8164D9AA1413F12708A3AE25E89D9%40YT3PR01MB8164.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] DS6 Database Question - "resourcepolicy" table

[Sean Kalynuk]

Hi John,

Some more info here:

https://wiki.lyrasis.org/display/DSDOC6x/Functional+Overview#FunctionalOverview-Authorization

Here’s a SQL case snippet you may find useful from one of my scripts:

case
when action_id=0  then 'READ'
when action_id=1  then 'WRITE'
when action_id=2  then 'DELETE'
when action_id=3  then 'ADD'
when action_id=4  then 'REMOVE'
when action_id=5  then 'WORKFLOW_STEP_1'
when action_id=6  then 'WORKFLOW_STEP_2'
when action_id=7  then 'WORKFLOW_STEP_3'
when action_id=8  then 'WORKFLOW_ABORT'
when action_id=9  then 'DEFAULT_BITSTREAM_READ'
when action_id=10 then 'DEFAULT_ITEM_READ'
when action_id=11 then 'ADMIN'
when action_id=12 then 'WITHDRAWN_READ'
else 'UNKNOWN'
end

Action constants are defined in this source file:

https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/core/Constants.java

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
John Fitzgerald 
Date: Wednesday, July 27, 2022 at 1:28 PM
To: DSpace Technical Support 
Subject: [dspace-tech] DS6 Database Question - "resourcepolicy" table
Caution: This message was sent from outside the University of Manitoba.

Howdy,

Would someone please clue me in on what the "action_id" field in the 
"resourcepolicy" table  is plugged into? I see no descriptive reference to it 
in any other tables.

I'm trying to write some SQL-scripts to audit permissions on a large repository.

Thanks,
-John
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/5ba40dcc-e3a4-4218-809d-d88f2c1ff3a8n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB8164E5C80E08B08807036D61E8979%40YT3PR01MB8164.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] info

[Sean Kalynuk]

Looks like this bug reported for DSpace 7.x:

https://github.com/DSpace/DSpace/issues/8376

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Massimiliano CILURZO 
Date: Monday, July 18, 2022 at 6:00 AM
To: DSpace Technical Support 
Subject: [dspace-tech] info
Caution: This message was sent from outside the University of Manitoba.

  Dear all,

  I have done a request a years ago with this problem but I haven't recived any 
answer.
I'll ask you agaen.
 We are using DSPACE 6.3, to update our OAI index we tried to this command:
/dspace oai import -o
But the system answer with this error:
OAI 2.0 manager action started

OAI 2.0 manager action started
Incremental import. Searching for documents modified after: Tue Oct 19 14:06:39 
CEST 2021
java.lang.IndexOutOfBoundsException: Index: 10, Size: 10
at java.util.ArrayList.rangeCheck(ArrayList.java:657)
at java.util.ArrayList.get(ArrayList.java:433)
at 
org.dspace.xoai.app.XOAI.getItemsWithPossibleChangesBefore(XOAI.java:206)
at org.dspace.xoai.app.XOAI.index(XOAI.java:177)
at org.dspace.xoai.app.XOAI.index(XOAI.java:145)
at org.dspace.xoai.app.XOAI.main(XOAI.java:560)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)

We tried to rebuild all index with
/dspace oai import -c
and this works fine.
But the incremental import does'nt work.

So I wonder why I have an index out bound excepition when I do an incremental 
update of the index?

Thanks
Best regards
Massimiliano

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/39886f1d-222a-4f8a-85c2-bc9265315559n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB8164779C9D4176E9A4E53545E88C9%40YT3PR01MB8164.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] DSpace 6.3 "Browse by"

[Sean Kalynuk]

It might be this bug:

https://github.com/DSpace/DSpace/issues/7292

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
ArunendraMB 
Date: Monday, July 4, 2022 at 8:58 AM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] DSpace 6.3 "Browse by"
Caution: This message was sent from outside the University of Manitoba.

Can anyone respond please?

On Mon, 27 Jun 2022, 19:48 Projects Arunendra, 
mailto:project.arunen...@gmail.com>> wrote:
Say there are 3 items with titles Abc, Mnp and Xyz.

If browse by Titles and give Abc in the search box, the result appears as Abc 
followed by the other 2 in alphabetical order.
Then, if I search Xyz, I get only Xyz as the result.
But, after this if I give Mnp, there is no result. The previous result of Xyz 
still remains.

Is it a bug?


From,
Arunendra MB.
India.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to a topic in the Google 
Groups "DSpace Technical Support" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/dspace-tech/F6iwjcR5ghw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/9ecf53ac-7f5f-48d5-a78d-c2a21023f9a0n%40googlegroups.com.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAO_tGrKwXs9uNezOBoy%3D7BOWVG-f9F0jgmTUBJe6VgVuuxwFnQ%40mail.gmail.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB81645042AA382AD79E845AF5E8BE9%40YT3PR01MB8164.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] How do I increase the size of files to upload?

[Sean Kalynuk]

So, you don’t have an upload issue, but instead have a download issue.

You will want to increase this parameter in your local.cfg or dspace.cfg file:

xmlui.content_disposition_threshold

See: 
https://wiki.lyrasis.org/display/DSDOC6x/Configuration+Reference#ConfigurationReference-ContentInlineDispositionThreshold

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Ronald Brenes Arce 
Date: Wednesday, June 29, 2022 at 5:36 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] How do I increase the size of files to upload?
Caution: This message was sent from outside the University of Manitoba.

The version is 6.3, what I do is upload videos and then be able to have a 
gallery to view them. when I upload videos smaller than 5Mb they play without 
problem, when they are larger they don't play but are downloaded automatically. 
I need to be able to view all the videos as if they were all the same size.

Thanks

El miércoles, 29 de junio de 2022 a las 14:57:32 UTC-6, sean.k...@umanitoba.ca 
escribió:
DSpace 6.3 should allow for at least 2GB based on the 
org.apache.cocoon.uploads.maxsize setting in 
webapps/xmlui/WEB-INF/cocoon/properties/core.properties

Lots of useful info in the discussions from an old bug resolved in DSpace 6.1:

https://github.com/DSpace/DSpace/issues/5724

If Tomcat is behind an Apache/nginx proxy, there are limits imposed at the 
proxy layer that you should check as well.

--
Sean

From: dspac...@googlegroups.com  on behalf of Ronald 
Brenes Arce 
Date: Wednesday, June 29, 2022 at 3:24 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] How do I increase the size of files to upload?
Caution: This message was sent from outside the University of Manitoba.

Dspace 6.3 XMLUI
El miércoles, 29 de junio de 2022 a las 13:37:11 UTC-6, sean.k...@umanitoba.ca 
escribió:
Is this for DSpace 6 JSPUI or XMLUI? Or for DSpace 7?
--
Sean

From: dspac...@googlegroups.com  on behalf of Ronald 
Brenes Arce 
Date: Monday, June 27, 2022 at 4:59 PM
To: DSpace Technical Support 
Subject: [dspace-tech] How do I increase the size of files to upload?
Caution: This message was sent from outside the University of Manitoba.

Hi

I have an issue and i can't troubleshoot, only can upload files less than 5Mb 
of size, and i need upload videos to more size.

Someone could tell me how i can change it?

Please.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/25d508bd-03cc-4dbd-969a-2abcc62eab18n%40googlegroups.com.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/d081e091-2405-4845-92c2-83ae4035cc68n%40googlegroups.com.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/aa79919f-e14b-44f3-abc6-65acd7b53ac9n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB81648FD6FAC64C35142547EEE8BA9%40YT3PR01MB8164.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] How do I increase the size of files to upload?

[Sean Kalynuk]

DSpace 6.3 should allow for at least 2GB based on the 
org.apache.cocoon.uploads.maxsize setting in 
webapps/xmlui/WEB-INF/cocoon/properties/core.properties

Lots of useful info in the discussions from an old bug resolved in DSpace 6.1:

https://github.com/DSpace/DSpace/issues/5724

If Tomcat is behind an Apache/nginx proxy, there are limits imposed at the 
proxy layer that you should check as well.

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Ronald Brenes Arce 
Date: Wednesday, June 29, 2022 at 3:24 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] How do I increase the size of files to upload?
Caution: This message was sent from outside the University of Manitoba.

Dspace 6.3 XMLUI
El miércoles, 29 de junio de 2022 a las 13:37:11 UTC-6, sean.k...@umanitoba.ca 
escribió:
Is this for DSpace 6 JSPUI or XMLUI? Or for DSpace 7?
--
Sean

From: dspac...@googlegroups.com  on behalf of Ronald 
Brenes Arce 
Date: Monday, June 27, 2022 at 4:59 PM
To: DSpace Technical Support 
Subject: [dspace-tech] How do I increase the size of files to upload?
Caution: This message was sent from outside the University of Manitoba.

Hi

I have an issue and i can't troubleshoot, only can upload files less than 5Mb 
of size, and i need upload videos to more size.

Someone could tell me how i can change it?

Please.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/25d508bd-03cc-4dbd-969a-2abcc62eab18n%40googlegroups.com.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/d081e091-2405-4845-92c2-83ae4035cc68n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB8164A6804D7AF0693EF8917DE8BB9%40YT3PR01MB8164.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] How do I increase the size of files to upload?

[Sean Kalynuk]

Is this for DSpace 6 JSPUI or XMLUI? Or for DSpace 7?
--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Ronald Brenes Arce 
Date: Monday, June 27, 2022 at 4:59 PM
To: DSpace Technical Support 
Subject: [dspace-tech] How do I increase the size of files to upload?
Caution: This message was sent from outside the University of Manitoba.

Hi

I have an issue and i can't troubleshoot, only can upload files less than 5Mb 
of size, and i need upload videos to more size.

Someone could tell me how i can change it?

Please.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/25d508bd-03cc-4dbd-969a-2abcc62eab18n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB8164FAA40E6C050B48520C4FE8BB9%40YT3PR01MB8164.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Submission Form - controlled input values

[Sean Kalynuk]

Hi Agustín,

The feature isn’t available in DSpace 6.x as far as I’m aware of, but it is 
available in DSpace 7 by using the regex element:

https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface#SubmissionUserInterface-CompositionofaField

--
Sean

From: 'Agustín Alfieri' via DSpace Technical Support 

Date: Thursday, June 16, 2022 at 7:12 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Submission Form - controlled input values
Caution: This message was sent from outside the University of Manitoba.

Hi!
Is there a way to only allow certain formats of values to be available when 
doing a submission? For example, for the field "Page Range" i want the user to 
only be able to put numbers in this format "xxx-xxx" (where x is any number).
Is there a feature to do this? I'm currently working with Dspace 6.3

Agustín.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/8fed4b83-46d0-4db0-bbb9-4a6238955f39n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YT3PR01MB816431DDC982156D92D641A0E8BB9%40YT3PR01MB8164.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] error building

[Sean Kalynuk]

I build everything as the same user and have most components installed locally 
to my account.

Here are the versions I used to set up the environment and compile (on RHEL 7):

openjdk 1.8.0_332 (global install)
mvn 3.3.9 (global install)
ant 1.9.4 (global install)
nvm 0.39.1 (local install)
node v12.22.12 (local install using nvm)
npm 6.14.16 (local install using nvm)
bower 1.8.14 (local install using local npm)
grunt 1.5.2 (local install using local npm)
grunt-cli v1.4.3 (local install using local npm)
rvm 1.29.12 (local install)
ruby 2.2.10p489 (2018-03-28 revision 63023) [x86_64-linux] (local install using 
local rvm)
gem 3.0.9 (local install along with local ruby)
sass 3.3.14 (local install using local gem)
ffi 1.12.2 (had to install this version before compass to be compatible with 
Ruby 2.2)
compass 1.0.1 (local install using local gem)

I do have root access to the host (via sudo) and did require that during the 
ruby install so that some required CentOS/RHEL packages could be installed.

--
Sean

From: Jose Blanco 
Date: Wednesday, May 4, 2022 at 10:24 AM
To: Sean Kalynuk 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Sean,

We have a few different things going on over here. I wonder if when you did all 
those installations, did you do it as the same user that builds dspace?

Because of permissions and accounts, I  could not do that.


Thank you!
-Jose

On Wed, May 4, 2022 at 9:49 AM Jose Blanco 
mailto:blan...@umich.edu>> wrote:
Now, I'm getting this error:


[ERROR] org.codehaus.plexus.archiver.ArchiverException: Failed setting file 
attributes with java7+: 
.../dspace/dspace/modules/xmlui-mirage2/target/mirage2-source-extracted/bower.json:
 Operation not permitted





I have installed the code required.  I could not install ruby as my own user, 
so I had a sys admin install it as root.  Does this ring a bell?



This is from running:



mvn clean package -Dmirage2.on=true -Dmirage2.deps.included=false



Very grateful for your help!!!



-Jose

On Tue, May 3, 2022 at 8:53 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
In our environment, I build using my personal account, then run any ant 
commands as the dspace user to do installs/updates. I just make sure that the 
dspace account has read-access to the build targets in my account’s directory.
--
Sean

From: Jose Blanco mailto:blan...@umich.edu>>
Date: Tuesday, May 3, 2022 at 5:45 PM
To: Sean Kalynuk mailto:sean.kaly...@umanitoba.ca>>
Cc: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Sean,  You know the way I work here, I log in as myself then I become the 
dspace user.  So I just tried doing this as myself and it worked.  I was trying 
to do the installation as a dspace user.

When I build dspace normally, I am the dspace user.  I wonder if I can do all 
these installations as myself and then build dspace as a dspace user. Do you 
think that will work?

Thank you!
-Jose

On Tue, May 3, 2022 at 5:55 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
Not sure. I installed nvm locally to my account with:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash

Logged out and back in and then ran:

nvm install 12
nvm alias default 12

In my environment, this gets added to my .bashrc:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This 
loads nvm bash_completion

--
Sean

From: Jose Blanco mailto:blan...@umich.edu>>
Date: Tuesday, May 3, 2022 at 4:46 PM
To: Sean Kalynuk mailto:sean.kaly...@umanitoba.ca>>
Cc: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Sean,

Sorry to bother you, I just tried again and it fails like this:


if [ ! -r node -o ! -L node ]; then \

  ln -fs out/Release/node node; fi

ln: failed to create symbolic link 'node': Operation not supported

Makefile:104: recipe for target 'node' failed

make: *** [node] Error 1

nvm: install v12.22.12 failed!





Why?



-Jose

On Tue, May 3, 2022 at 4:36 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
Hi Jose,

Sorry, I don’t know about the status of torquebox.org<http://torquebox.org>, 
but since there have been issues with that domain before, I’m sticking with the 
locally installed Mirage 2 prerequisites now since I managed to get a full 
compile.

When you installed nvm, it would have modified your account’s login scripts. In 
my case, it modified my .bashrc file. I logged out and back in again to

Re: [dspace-tech] error building

[Sean Kalynuk]

In our environment, I build using my personal account, then run any ant 
commands as the dspace user to do installs/updates. I just make sure that the 
dspace account has read-access to the build targets in my account’s directory.
--
Sean

From: Jose Blanco 
Date: Tuesday, May 3, 2022 at 5:45 PM
To: Sean Kalynuk 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Sean,  You know the way I work here, I log in as myself then I become the 
dspace user.  So I just tried doing this as myself and it worked.  I was trying 
to do the installation as a dspace user.

When I build dspace normally, I am the dspace user.  I wonder if I can do all 
these installations as myself and then build dspace as a dspace user. Do you 
think that will work?

Thank you!
-Jose

On Tue, May 3, 2022 at 5:55 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
Not sure. I installed nvm locally to my account with:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash

Logged out and back in and then ran:

nvm install 12
nvm alias default 12

In my environment, this gets added to my .bashrc:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This 
loads nvm bash_completion

--
Sean

From: Jose Blanco mailto:blan...@umich.edu>>
Date: Tuesday, May 3, 2022 at 4:46 PM
To: Sean Kalynuk mailto:sean.kaly...@umanitoba.ca>>
Cc: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Sean,

Sorry to bother you, I just tried again and it fails like this:


if [ ! -r node -o ! -L node ]; then \

  ln -fs out/Release/node node; fi

ln: failed to create symbolic link 'node': Operation not supported

Makefile:104: recipe for target 'node' failed

make: *** [node] Error 1

nvm: install v12.22.12 failed!





Why?



-Jose

On Tue, May 3, 2022 at 4:36 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
Hi Jose,

Sorry, I don’t know about the status of torquebox.org<http://torquebox.org>, 
but since there have been issues with that domain before, I’m sticking with the 
locally installed Mirage 2 prerequisites now since I managed to get a full 
compile.

When you installed nvm, it would have modified your account’s login scripts. In 
my case, it modified my .bashrc file. I logged out and back in again to make 
sure I had the right environment settings before running “nvm install 12”.

--
Sean

From: Jose Blanco mailto:blan...@umich.edu>>
Date: Tuesday, May 3, 2022 at 3:12 PM
To: Sean Kalynuk mailto:sean.kaly...@umanitoba.ca>>
Cc: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Sean, I'm doing the install and it takes a while and now I'm getting :


nvm: install v12.22.12 failed!



is there any chance we will be able to build without having to do this?



-Jose

On Tue, May 3, 2022 at 3:08 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
The torquebox.org<http://torquebox.org> domain has expired.

See old discussion: https://groups.google.com/g/dspace-tech/c/RPL_qoTGvMI

The workaround is to install the prerequisite software for building Mirage 2:

https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2#installation

I’m currently setting up the workaround myself since I ran into this yesterday 
and can’t wait for torquebox.org<http://torquebox.org> to return. Will be more 
stable (and faster!) for builds in the long run too.

--
Sean

From: dspace-tech@googlegroups.com<mailto:dspace-tech@googlegroups.com> 
mailto:dspace-tech@googlegroups.com>> on behalf 
of Jose Blanco mailto:blan...@umich.edu>>
Date: Tuesday, May 3, 2022 at 1:47 PM
To: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Getting this error when building 6.3.  It was working fine a week ago


[ERROR] Failed to execute goal on project xmlui-mirage2: Could not resolve 
dependencies for project org.dspace.modules:xmlui-mirage2:war:6.3: Failed to 
collect dependencies at rubygems:compass:gem:1.0.1 -> 
rubygems:sass:gem:[3.3.13,3.5): No versions available for 
rubygems:sass:gem:[3.3.13,3.5) within specified range -> [Help 1]



-Jose
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Techni

Re: [dspace-tech] error building

[Sean Kalynuk]

Not sure. I installed nvm locally to my account with:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash

Logged out and back in and then ran:

nvm install 12
nvm alias default 12

In my environment, this gets added to my .bashrc:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This 
loads nvm bash_completion

--
Sean

From: Jose Blanco 
Date: Tuesday, May 3, 2022 at 4:46 PM
To: Sean Kalynuk 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Sean,

Sorry to bother you, I just tried again and it fails like this:


if [ ! -r node -o ! -L node ]; then \

  ln -fs out/Release/node node; fi

ln: failed to create symbolic link 'node': Operation not supported

Makefile:104: recipe for target 'node' failed

make: *** [node] Error 1

nvm: install v12.22.12 failed!





Why?



-Jose

On Tue, May 3, 2022 at 4:36 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
Hi Jose,

Sorry, I don’t know about the status of torquebox.org<http://torquebox.org>, 
but since there have been issues with that domain before, I’m sticking with the 
locally installed Mirage 2 prerequisites now since I managed to get a full 
compile.

When you installed nvm, it would have modified your account’s login scripts. In 
my case, it modified my .bashrc file. I logged out and back in again to make 
sure I had the right environment settings before running “nvm install 12”.

--
Sean

From: Jose Blanco mailto:blan...@umich.edu>>
Date: Tuesday, May 3, 2022 at 3:12 PM
To: Sean Kalynuk mailto:sean.kaly...@umanitoba.ca>>
Cc: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Sean, I'm doing the install and it takes a while and now I'm getting :


nvm: install v12.22.12 failed!



is there any chance we will be able to build without having to do this?



-Jose

On Tue, May 3, 2022 at 3:08 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
The torquebox.org<http://torquebox.org> domain has expired.

See old discussion: https://groups.google.com/g/dspace-tech/c/RPL_qoTGvMI

The workaround is to install the prerequisite software for building Mirage 2:

https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2#installation

I’m currently setting up the workaround myself since I ran into this yesterday 
and can’t wait for torquebox.org<http://torquebox.org> to return. Will be more 
stable (and faster!) for builds in the long run too.

--
Sean

From: dspace-tech@googlegroups.com<mailto:dspace-tech@googlegroups.com> 
mailto:dspace-tech@googlegroups.com>> on behalf 
of Jose Blanco mailto:blan...@umich.edu>>
Date: Tuesday, May 3, 2022 at 1:47 PM
To: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Getting this error when building 6.3.  It was working fine a week ago


[ERROR] Failed to execute goal on project xmlui-mirage2: Could not resolve 
dependencies for project org.dspace.modules:xmlui-mirage2:war:6.3: Failed to 
collect dependencies at rubygems:compass:gem:1.0.1 -> 
rubygems:sass:gem:[3.3.13,3.5): No versions available for 
rubygems:sass:gem:[3.3.13,3.5) within specified range -> [Help 1]



-Jose
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-s6a-G-N_1sQGNmBc8E%3DVR82c%3Dt%2BZV2%3DUfC-Wu5b-6iSw%40mail.gmail.com<https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-s6a-G-N_1sQGNmBc8E%3DVR82c%3Dt%2BZV2%3DUfC-Wu5b-6iSw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YQBPR0101MB54042EB8FEA1324C27E7FBB5E8C09%40YQBPR0101MB5404.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] error building

[Sean Kalynuk]

Hi Jose,

Sorry, I don’t know about the status of torquebox.org, but since there have 
been issues with that domain before, I’m sticking with the locally installed 
Mirage 2 prerequisites now since I managed to get a full compile.

When you installed nvm, it would have modified your account’s login scripts. In 
my case, it modified my .bashrc file. I logged out and back in again to make 
sure I had the right environment settings before running “nvm install 12”.

--
Sean

From: Jose Blanco 
Date: Tuesday, May 3, 2022 at 3:12 PM
To: Sean Kalynuk 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Sean, I'm doing the install and it takes a while and now I'm getting :


nvm: install v12.22.12 failed!



is there any chance we will be able to build without having to do this?



-Jose

On Tue, May 3, 2022 at 3:08 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
The torquebox.org<http://torquebox.org> domain has expired.

See old discussion: https://groups.google.com/g/dspace-tech/c/RPL_qoTGvMI

The workaround is to install the prerequisite software for building Mirage 2:

https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2#installation

I’m currently setting up the workaround myself since I ran into this yesterday 
and can’t wait for torquebox.org<http://torquebox.org> to return. Will be more 
stable (and faster!) for builds in the long run too.

--
Sean

From: dspace-tech@googlegroups.com<mailto:dspace-tech@googlegroups.com> 
mailto:dspace-tech@googlegroups.com>> on behalf 
of Jose Blanco mailto:blan...@umich.edu>>
Date: Tuesday, May 3, 2022 at 1:47 PM
To: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Getting this error when building 6.3.  It was working fine a week ago


[ERROR] Failed to execute goal on project xmlui-mirage2: Could not resolve 
dependencies for project org.dspace.modules:xmlui-mirage2:war:6.3: Failed to 
collect dependencies at rubygems:compass:gem:1.0.1 -> 
rubygems:sass:gem:[3.3.13,3.5): No versions available for 
rubygems:sass:gem:[3.3.13,3.5) within specified range -> [Help 1]



-Jose
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-s6a-G-N_1sQGNmBc8E%3DVR82c%3Dt%2BZV2%3DUfC-Wu5b-6iSw%40mail.gmail.com<https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-s6a-G-N_1sQGNmBc8E%3DVR82c%3Dt%2BZV2%3DUfC-Wu5b-6iSw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YQBPR0101MB5404168DE7492C8B194AC8E6E8C09%40YQBPR0101MB5404.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] error building

[Sean Kalynuk]

The torquebox.org domain has expired.

See old discussion: https://groups.google.com/g/dspace-tech/c/RPL_qoTGvMI

The workaround is to install the prerequisite software for building Mirage 2:

https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2#installation

I’m currently setting up the workaround myself since I ran into this yesterday 
and can’t wait for torquebox.org to return. Will be more stable (and faster!) 
for builds in the long run too.

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Jose Blanco 
Date: Tuesday, May 3, 2022 at 1:47 PM
To: DSpace Technical Support 
Subject: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

Getting this error when building 6.3.  It was working fine a week ago


[ERROR] Failed to execute goal on project xmlui-mirage2: Could not resolve 
dependencies for project org.dspace.modules:xmlui-mirage2:war:6.3: Failed to 
collect dependencies at rubygems:compass:gem:1.0.1 -> 
rubygems:sass:gem:[3.3.13,3.5): No versions available for 
rubygems:sass:gem:[3.3.13,3.5) within specified range -> [Help 1]



-Jose
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-s6a-G-N_1sQGNmBc8E%3DVR82c%3Dt%2BZV2%3DUfC-Wu5b-6iSw%40mail.gmail.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YQBPR0101MB54040349EA48901F5CDE7194E8C09%40YQBPR0101MB5404.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Discovery Date Range Queries (DSpace 6)

[Sean Kalynuk]

Hi,

You could try using the Solr range query syntax with the Equals comparison:

[2021-03-01 TO 2021-05-31]

DSpace 6.3 uses Solr 4.10.4, so additional information on range queries can be 
found in:

http://archive.apache.org/dist/lucene/solr/ref-guide/apache-solr-ref-guide-4.10.pdf

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
kpet 
Date: Wednesday, November 17, 2021 at 5:32 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Discovery Date Range Queries (DSpace 6)
Caution: This message was sent from outside the University of Manitoba.
Hello,

I have a DSpace 6.3 installed on a linux machine, using tomcat 9, jre 1.8, ant 
1.10 and maven 3.3.9.

I want to be able to perform a search query via the Discovery interface on a 
date field (e.g. dc.date.available) but for a date range, for example objects 
returned should have dc.date.available between March and May of 2021, i.e. 
dc.date.available >= 2021-03-01 && dc.date.available <= 2021-05-31

I have read the documentation of Discovery on how to add custom search filters 
but the problem is I also want to add a custom relational operator, as in 
"greater than". Currently, I only see Contains, Equals, ID, Not Contains, Not 
Equals, Not ID.

Any help would be greatly appreciated.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/6d8c8661-d9e1-4e19-a6e6-93e17277e73fn%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YQBPR0101MB5404DCD23DD7AA6613C331F5E8619%40YQBPR0101MB5404.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] assetstore too large for dev instance

[Sean Kalynuk]

Hi Paul,

Are you able to mount the production assetstore on your dev instance via NFS in 
read-only mode? Or, if not that, use SSHFS instead?

If you can mount the remote filesystem read-only, you can adjust the 
bitstore.xml configuration on the dev instance to have two storage locations: 
one for the original production read-only data, and then a new writeable one 
for dev to be used for testing. Then make sure the “incoming” storage location 
is set to the writeable dev filesystem.

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
paulw...@gmail.com 
Date: Monday, November 15, 2021 at 2:27 AM
To: DSpace Technical Support 
Subject: [dspace-tech] assetstore too large for dev instance
Caution: This message was sent from outside the University of Manitoba.
Hi,

We are running a DSpace instance with a very large assetstore (over 1.2 TB), 
and this is now too large for our dev instance.  We do not have enough disk 
space.  Is there a way to strip the assetstore of content, use dummy files, or 
otherwise empty the assetstore for the dev instance?  We sync the database to 
the dev instance.  We are considering running the dev instance on the same 
machine, in which case, could we use the same assetstore for the dev instance?  
How would we set that up?

We are using DSpace 6.3 on SUSE Linux Enterprise Server with PostgreSQL.

Thanks for any suggestions,
Paul
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/3808102f-27e4-4dd6-b24e-d7b38e441255n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YQBPR0101MB5404B0F4CEE597AFFA1A4440E8989%40YQBPR0101MB5404.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Re: Orcid patching failure function

[Sean Kalynuk]

Hi Ghazi,

Some issues with that patch and also issues in DSpace 6.3 that affect 
behaviour. See my older comments here:

https://groups.google.com/g/dspace-tech/c/N4f5aZJyHKg/m/R1s1WM_gAgAJ

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Ghazi Putra 
Date: Saturday, June 5, 2021 at 3:55 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: Orcid patching failure function
Caution: This message was sent from outside the University of Manitoba.
Also i just run this script :
Run /dspace/bin/dspace index-authority
Run /dspace/bin/dspace index-discovery

but still nothing happen,

Thank you,
Ghazi

On Saturday, June 5, 2021 at 4:53:10 PM UTC+8 Ghazi Putra wrote:

Hi everyone,

i just finished installing dspace 6.3 and pathcing orcid using this : 
https://github.com/atmire/expanded-ORCID-support

Everything is fine, no indication of error during installation or patching, im 
using mvn package -Dmirage2.on=true .

The problem I'm facing is that the author link on the submission can't be 
clicked and the orcid logo doesn't appear, the logo should appear right?
[https://groups.google.com/group/dspace-tech/attach/b2118ffdffa08/dspace1.jpg?part=0.1&view=1]


Thankyou,
Ghazi
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/62ebc3e5-5c29-4257-a1c4-01ab911b3885n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB0848E0012EE346705F441858E8399%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

[dspace-tech] Re: Save & Exit button not working for textarea fields in workflow tasks

[Sean Kalynuk]

Hi Donna,

I found this reported issue:

https://jira.lyrasis.org/browse/DS-4157

I can confirm that the problem exists with our DSpace instance as well. There 
is a pull request linked to the issue but I haven’t tried the patch yet.

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Donna Barber 
Date: Sunday, May 16, 2021 at 4:54 PM
To: dspace-tech@googlegroups.com 
Subject: [dspace-tech] Save & Exit button not working for textarea fields in 
workflow tasks

Caution: This message was sent from outside the University of Manitoba.


Hi all,

We've noticed what we think is a minor (but annoying) bug with the submission 
form, where the Save & Exit button is functioning like a Cancel button. This is 
only occurring during workflow tasks - the behaviour is different for an 
initial submission.

The problem is that data entered into any textarea type input is only saved 
when progressing through the form using either the Previous or Next buttons. If 
the user selects Save & Exit, any new text added to these fields on the current 
tab is lost.

We're on DSpace 6.3 using Mirage 2, and I've tested on the demo site and had 
the same problem. Is it possible to add this to the list of issues to be fixed?

Many thanks,
Donna

Donna Barber
Kairuruku Ratonga Matihiko | Digital Services Coordinator
Rōpū Tautāwhi | Library Access and Collections
Phone: +64 3 369 3849 extn 93849 | Puaka - James Hight Building, Level 5, Rm 519
Te Whare Wānanga o Waitaha | University of Canterbury | Private Bag 4800 | 
Christchurch 8140 | New Zealand
Website: http://www.canterbury.ac.nz/library

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/SYBPR01MB42208C99F6C909C840B5BB0EBF2E9%40SYBPR01MB4220.ausprd01.prod.outlook.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB084872EDD5B500DE6A04D6B1E82C9%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

[dspace-tech] Re: Assigning DOIs automatically for a single community

[Sean Kalynuk]

Hi Gail,

There is a feature request for that functionality in DSpace 7, although it 
doesn’t look like it has been implemented yet:

https://jira.lyrasis.org/browse/DS-3749

As far as I can tell, DSpace 6 has DOI assignment for the whole repository, or 
nothing at all.

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Gail Steinhart 
Date: Monday, May 10, 2021 at 1:56 PM
To: dspace-tech@googlegroups.com 
Subject: [dspace-tech] Assigning DOIs automatically for a single community
Caution: This message was sent from outside the University of Manitoba.
Greetings all and with apologies for posting to both lists.

We have a use case where a community would like DOIs assigned to items in all 
their collections automatically, but we do not want to do that across the 
entire repository. Does anyone know if this is possible, and better still, is 
anyone actually doing it? DSpace documentation is written for implementation 
across the repository (understandable), so I can’t tell whether it’s not 
possible or whether it simply not documented.

Thanks so much,
Gail

Gail Steinhart
Open Scholarship Services Librarian
Cornell University Library Information Technology
218 Olin Library | 607.255.7251
https://orcid.org/-0002-2441-1651 | @gailst
she/her

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/1FF1987A-783E-4893-91D1-CC1390394370%40cornell.edu.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB08482B117FE3D38D08434CBEE8549%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] How do I create an exclusion list for filter-media?

[Sean Kalynuk]

Hi Kerry,

There is a Skip mode option (-s) for the filter-media command:

https://wiki.lyrasis.org/display/DSDOC6x/Mediafilters+for+Transforming+DSpace+Content#MediafiltersforTransformingDSpaceContent-Executing(viaCommandLine)

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Kerry Bouchard 
Date: Wednesday, May 5, 2021 at 3:20 PM
To: DSpace Technical Support 
Subject: [dspace-tech] How do I create an exclusion list for filter-media?
Caution: This message was sent from outside the University of Manitoba.
We are running into the problem described here: 
http://dspace.2283337.n4.nabble.com/Filter-media-on-PDFs-exported-from-Outlook-causes-a-TikaException-error-and-prevents-Items-from-inde-td4683489.html
 , where the *.pdf.txt files output by the PDF Text Extractor media filter for 
a couple of PDFs in our repository causes indexing to fail for not just the PDF 
full text, but all the associated metadata. (In our case, the PDFs were not 
output from Microsoft Outlook mail folders, but I'm seeing the same 
"org.apache.tika.exception.TikaException: Failed to parse an email message" in 
the dspace log file.)

The posting at the URL above refers to a work-around by creating an exclusion 
list for filter-media. But I can find any documentation on how to create an 
exclusion list. Can someone point me to that?

Thanks, Kerry
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/85e9b754-31d4-4558-8bde-071facdf9d0bn%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB08480475F87E87D0014942DEE8599%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] access bundle in workflow

[Sean Kalynuk]

Hi Florian,

You can search for the item UUID in the /admin/item page if you are an 
administrator. When you select the item in the workflow to view it, the item 
UUID is in the URLs for the submitted files (which are /bitstream/item/UUID/…).

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Florian Wille 
Date: Monday, May 3, 2021 at 9:23 AM
To: DSpace Technical Support 
Subject: [dspace-tech] access bundle in workflow
Hey there!

I remember accessing the bundle view of an item still in the workflow in
a DSpace 6.3 with XMLUI but can't seem to find the right link anymore.
Could someone please givve me a hint?

THX
Florian

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/efa89268-6a01-13cd-57c6-6532609e1d74%40ub.fu-berlin.de.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB0848A996691D1FD0D1D0CAEFE85B9%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] How to view the XML DRI framework from the home page

[Sean Kalynuk]

One thing to add is that, if you are using Mirage 2, the /DRI path approach 
shows you the DRI before preprocess.xsl is applied. Using the ?XML approach 
shows you the DRI after preprocess.xsl is applied.
--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Matheus Silva 
Date: Thursday, April 15, 2021 at 12:25 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] How to view the XML DRI framework from the home page
Caution: This message was sent from outside the University of Manitoba.
Thank you so much guys! Worked perfectly!
On Thursday, April 15, 2021 at 2:01:02 PM UTC-3 Adan Roman Ruiz wrote:
Hi

You only need to add /DRI/ after xmlui

the home DRI is:
https://demo.dspace.org/xmlui/DRI/

and other's page DRI:
https://demo.dspace.org/xmlui/DRI/handle/10673/1

Regards
Adán


Hello guys, how are you?
I need to see the DRI structure that dspace builds on its home page. Anybody 
know?

Example:

I have this item on the dspace https://demo.dspace.org/xmlui/handle/10673/89
Error! Filename not specified.

To see the structure of the xml DRI just add? XML in the url, it looks like 
this:

https://demo.dspace.org/xmlui/handle/10673/89?XML
Error! Filename not specified.

but when I try to see the XML from the main page of the dspace I can't. Does 
anyone know how to see?

https://demo.dspace.org/xmlui?XML

BR,
Matheus Silva
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/c994bf1c--4484-811b-8ea548a4efa0n%40googlegroups.com.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/14afcaac-9a75-4895-816a-0679d47219b9n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB08483A850298F1302B91C09EE84D9%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] How to view the XML DRI framework from the home page

[Sean Kalynuk]

Hi Matheus,

Add a slash before the question mark:

https://demo.dspace.org/xmlui/?XML

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Matheus Silva 
Date: Thursday, April 15, 2021 at 10:48 AM
To: DSpace Technical Support 
Subject: [dspace-tech] How to view the XML DRI framework from the home page
Caution: This message was sent from outside the University of Manitoba.
Hello guys, how are you?
I need to see the DRI structure that dspace builds on its home page. Anybody 
know?

Example:

I have this item on the dspace https://demo.dspace.org/xmlui/handle/10673/89
[cid:image001.png@01D731E5.DF9CB560]

To see the structure of the xml DRI just add? XML in the url, it looks like 
this:

https://demo.dspace.org/xmlui/handle/10673/89?XML
[cid:image002.png@01D731E5.DF9CB560]

but when I try to see the XML from the main page of the dspace I can't. Does 
anyone know how to see?

https://demo.dspace.org/xmlui?XML

BR,
Matheus Silva
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/c994bf1c--4484-811b-8ea548a4efa0n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB08483D6EBC2CA8723B8E8DF9E84D9%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] identifier

[Sean Kalynuk]

Great to hear! A clean-cache worked for me too after editing the 
repositoryIdentifier. Nice to know that a webapp restart is not required.
--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Germán Morales G. 
Date: Wednesday, March 10, 2021 at 9:55 AM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] identifier
Caution: This message was sent from outside the University of Manitoba.
Thank you very much for your great help.

I rebooted the tomcat and the server but it didn't work, I used oai clea-cache 
and it got updated.

Greetings.
El miércoles, 10 de marzo de 2021 a la(s) 12:23:37 UTC-3, 
sean.k...@umanitoba.ca escribió:
The repository identifier can be set in:

/config/crosswalks/oai/description.xml

You might have to restart the oai webapp after editing the file.
--
Sean

From: dspac...@googlegroups.com  on behalf of Germán 
Morales G. 
Date: Wednesday, March 10, 2021 at 9:08 AM
To: DSpace Technical Support 
Subject: [dspace-tech] identifier
Caution: This message was sent from outside the University of Manitoba.
Good morning, could someone please tell me how or where to modify the text that 
says "localhost"?

this is in the url -> /oai/request?verb=Identify


[https://groups.google.com/group/dspace-tech/attach/166c55037fdf6/image001.png?part=0.1&view=1]
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/42e1a01f-901a-4ed5-870d-d35a032877d1n%40googlegroups.com.
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/a40ede34-299f-42ed-bdb2-f630dfc618fdn%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB0848E2C5B112ED610A7B47DBE8919%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] identifier

[Sean Kalynuk]

The repository identifier can be set in:

/config/crosswalks/oai/description.xml

You might have to restart the oai webapp after editing the file.
--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Germán Morales G. 
Date: Wednesday, March 10, 2021 at 9:08 AM
To: DSpace Technical Support 
Subject: [dspace-tech] identifier
Caution: This message was sent from outside the University of Manitoba.
Good morning, could someone please tell me how or where to modify the text that 
says "localhost"?

this is in the url -> /oai/request?verb=Identify


[cid:image001.png@01D7158F.08977810]
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/42e1a01f-901a-4ed5-870d-d35a032877d1n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB08484412C979815615E21569E8919%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] looking into using the ORCID functionality

[Sean Kalynuk]

You’re welcome. I hope I didn’t scare you. 😊 We do have the bare minimum ORCID 
support in production (with some of the known patches/fixes applied), but I 
still need to do a lot more testing before we can really commit to it.

BTW, there’s some better info on the Authority Control here:

https://wiki.lyrasis.org/display/DSPACE/Authority+Control+of+Metadata+Values

Also some better info on the confidence value than I originally provided:

https://wiki.lyrasis.org/display/DSPACE/Authority+Control+of+Metadata+Values#AuthorityControlofMetadataValues-Confidence

--
Sean

From: Jose Blanco 
Date: Tuesday, February 23, 2021 at 5:13 PM
To: Sean Kalynuk 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] looking into using the ORCID functionality
Caution: This message was sent from outside the University of Manitoba.
Sean, This is really helpful.  It really sounds like it's not that reliable, 
with all the issues, but I need to read your response more carefully.

Thank you
-Jose

On Tue, Feb 23, 2021 at 5:26 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
Hi Jose,

I’ve encountered a number of issues using the ORCID functionality in DSpace 
6.3, and I’m still working through them, but here’s some info based on my 
experience so far (numbered according to your questions):


  1.  index-authority will keep the Solr authority index up-to-date with 
respect to metadata in the database that is authority controlled. In regards to 
ORCID and dc.contributor.author, it does not use the ORCID API to find authors. 
(Important – See Issue: https://jira.lyrasis.org/browse/DS-3999) More details 
in the manual than I can include here 
(https://wiki.lyrasis.org/display/DSDOC6x/ORCID+Integration#ORCIDIntegration-Importingexistingauthors&keepingtheindexuptodate).
 Keep in mind that the first run will take a long time. In our environment I 
think I was only getting <2000 records created per hour. In addition to 
index-authority, in order to keep the ORCID information in the Solr authority 
index up-to-date, you’re supposed to run “dsrun 
org.dspace.authority.UpdateAuthorities” but there’s another issue as well - 
https://jira.lyrasis.org/browse/DS-3302. I don’t have an official patch for it 
yet, but the problem is that the default Solr query only checks 10 records. I 
only corrected this in our source code for now, and haven’t really had the time 
to test it fully.
  2.  Italicized authors in the lookup are the ones found using the ORCID API, 
whereas the non-italicized authors come from your Solr authority index. If you 
don’t apply the fix for DS-3999 you may see duplicates.
  3.  The ORCID iD is only displayed in the lookup dialog. However, if you 
apply the Expanded ORCID patch 
(https://atmire.github.io/expanded-ORCID-support/#/) a clickable icon is 
displayed next to authors’ names that have their ORCID iD assigned in DSpace. 
There are other features as well. (See issue 
https://github.com/atmire/expanded-ORCID-support/issues/3 with regards to the 
DS-3999 fix).
  4.  ORCID iDs can be populated manually via the lookup dialog (either via the 
admin-level metadata edit, or with a normal submission when adding authors), 
and also imported via the metadata import tool. Using the metadata import tool 
to do it 
(https://wiki.lyrasis.org/display/DSDOC7x/ORCID+Integration#ORCIDIntegration-EditingexistingitemsusingBatchCSVEditing)
 has its own quirks. Too many to go into here unfortunately, so I’d suggest 
doing a lot of testing before trying it in production.
  5.  The recommendation is to run index-authority once a day during off-hours. 
(The first run of index-authority takes a long time, but subsequent runs don’t 
take nearly as long. Some recent tests I did took about 1 hour to check and 
update about 30,000 records.) When you run UpdateAuthorities is dependent on 
your needs.
  6.  I was also surprised that the default DSpace 6.3 ORCID functionality did 
not include a proper item display of the ORCID iD along with the author name 
(or even a clickable link to the ORCID record). Sure, you can click the ORCID 
iD link in the lookup dialog, but that doesn’t apply for normal browsing. Other 
people obviously had the same reaction, hence the Expanded ORCID Support patch. 
Surprisingly, there is an icon displayed for the confidence level in the 
detailed metadata view (see more on the confidence in the next answer)
  7.  You’re correct that the authority key is the identifier that links the 
metadata record to a record in the Solr authority index. The confidence value 
is supposed to reflect different levels of confidence on the metadata value 
based on where the information was obtained, or who entered it. Again, lots of 
quirks on this one. Check out the source code to see an explanation of 
different values 
https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/content/authority/Choices.java.
 There’s also this issue: https://jira.lyrasis.org/browse/DS-39

Re: [dspace-tech] looking into using the ORCID functionality

[Sean Kalynuk]

Hi Jose,

I’ve encountered a number of issues using the ORCID functionality in DSpace 
6.3, and I’m still working through them, but here’s some info based on my 
experience so far (numbered according to your questions):


  1.  index-authority will keep the Solr authority index up-to-date with 
respect to metadata in the database that is authority controlled. In regards to 
ORCID and dc.contributor.author, it does not use the ORCID API to find authors. 
(Important – See Issue: https://jira.lyrasis.org/browse/DS-3999) More details 
in the manual than I can include here 
(https://wiki.lyrasis.org/display/DSDOC6x/ORCID+Integration#ORCIDIntegration-Importingexistingauthors&keepingtheindexuptodate).
 Keep in mind that the first run will take a long time. In our environment I 
think I was only getting <2000 records created per hour. In addition to 
index-authority, in order to keep the ORCID information in the Solr authority 
index up-to-date, you’re supposed to run “dsrun 
org.dspace.authority.UpdateAuthorities” but there’s another issue as well - 
https://jira.lyrasis.org/browse/DS-3302. I don’t have an official patch for it 
yet, but the problem is that the default Solr query only checks 10 records. I 
only corrected this in our source code for now, and haven’t really had the time 
to test it fully.
  2.  Italicized authors in the lookup are the ones found using the ORCID API, 
whereas the non-italicized authors come from your Solr authority index. If you 
don’t apply the fix for DS-3999 you may see duplicates.
  3.  The ORCID iD is only displayed in the lookup dialog. However, if you 
apply the Expanded ORCID patch 
(https://atmire.github.io/expanded-ORCID-support/#/) a clickable icon is 
displayed next to authors’ names that have their ORCID iD assigned in DSpace. 
There are other features as well. (See issue 
https://github.com/atmire/expanded-ORCID-support/issues/3 with regards to the 
DS-3999 fix).
  4.  ORCID iDs can be populated manually via the lookup dialog (either via the 
admin-level metadata edit, or with a normal submission when adding authors), 
and also imported via the metadata import tool. Using the metadata import tool 
to do it 
(https://wiki.lyrasis.org/display/DSDOC7x/ORCID+Integration#ORCIDIntegration-EditingexistingitemsusingBatchCSVEditing)
 has its own quirks. Too many to go into here unfortunately, so I’d suggest 
doing a lot of testing before trying it in production.
  5.  The recommendation is to run index-authority once a day during off-hours. 
(The first run of index-authority takes a long time, but subsequent runs don’t 
take nearly as long. Some recent tests I did took about 1 hour to check and 
update about 30,000 records.) When you run UpdateAuthorities is dependent on 
your needs.
  6.  I was also surprised that the default DSpace 6.3 ORCID functionality did 
not include a proper item display of the ORCID iD along with the author name 
(or even a clickable link to the ORCID record). Sure, you can click the ORCID 
iD link in the lookup dialog, but that doesn’t apply for normal browsing. Other 
people obviously had the same reaction, hence the Expanded ORCID Support patch. 
Surprisingly, there is an icon displayed for the confidence level in the 
detailed metadata view (see more on the confidence in the next answer)
  7.  You’re correct that the authority key is the identifier that links the 
metadata record to a record in the Solr authority index. The confidence value 
is supposed to reflect different levels of confidence on the metadata value 
based on where the information was obtained, or who entered it. Again, lots of 
quirks on this one. Check out the source code to see an explanation of 
different values 
https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/content/authority/Choices.java.
 There’s also this issue: https://jira.lyrasis.org/browse/DS-3994
  8.  All ORCID information is kept in the Solr authority index. Again, really 
important to get the fix for DS-3999 since if you don’t have it you can lose 
ORCID information.

--
Sean


I want to make sure I understand what the ORCID function in 6.3 provides.  So I 
have a few questions.

(1)  When you run
[dspace]/bin/dspace index-authority

this goes out to: https://pub.orcid.org/v2.1 (defined in 
dspace.cfg:orcid.api.url )

And creates records of them in the authority index.

Correct?

(2) After the solr authority index is created, depositors of items will be 
given a "Lookup" button for dc metadata configed, out of the box this is 
contributor.author.  The user can then click on this button and search for the 
author and select it. I'm a bit confused about the difference between the case 
when the selection presents the same author twice ( once italicized, and one 
not ).  What's the difference in selecting one from the other?

(3)  Do you ever see the ORCIDs for the authors in any of the Dspace pages? Say 
during the deposit, I select Smith, John with x ORCID, does this show up in t

Re: [dspace-tech] Metadata Import of CSV file stops when a field in the CSV file with new data matches a record where the corresponding field in the DSpace record contains blank/null data

[Sean Kalynuk]

Hi Kerry,

Please consult the support page, specifically the part that describes what to 
do if you’ve found a bug.

https://wiki.lyrasis.org/display/DSPACE/Support

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Kerry Bouchard 
Date: Monday, February 22, 2021 at 2:29 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] Metadata Import of CSV file stops when a field in 
the CSV file with new data matches a record where the corresponding field in 
the DSpace record contains blank/null data
Caution: This message was sent from outside the University of Manitoba.
Thanks for the suggested tests. I've confirmed that the same problem happens 
when I try the import from the command line rather than the web interface. And 
rearranging the order of columns in the spreadsheets doesn't make any 
difference. I can import the same data as new records, but that just confirms 
that the problem is triggered by empty metadata fields in existing records.

Is there a process for reporting an issue like this as a potential bug?

Thanks, Kerry

On Wednesday, February 17, 2021 at 10:43:30 AM UTC-6 sean.k...@umanitoba.ca 
wrote:
Hi Kerry,

Are you only importing the CSV file from the user interface? I wonder what 
would happen if you tried importing the metadata using the command-line tool. 
Since it’s the same core code that’s used, I’m guessing that the merge logic 
won’t be any different, but the method for transferring the CSV file to the 
server via the user interface is different than if you transferred the file 
yourself and used the command-line tool.

For your earlier tests with debugging turned on, see if there are lines in the 
log files that have the keyword metadata_import. (Note that I’m basing this on 
my knowledge of DSpace 6.3. If you have a much older version, the log entries 
might be different.) That information might give you a clue as to what is going 
on.

--
Sean

From: dspac...@googlegroups.com  on behalf of Kelley 
Canon 
Date: Monday, February 15, 2021 at 8:42 AM
To: Bouchard, Kerry 
Cc: dspac...@googlegroups.com 
Subject: Re: [dspace-tech] Metadata Import of CSV file stops when a field in 
the CSV file with new data matches a record where the corresponding field in 
the DSpace record contains blank/null data
Caution: This message was sent from outside the University of Manitoba.
Kerry -

I looked at your data and I don't see any problems.  dSpace should just 
overwrite the empty field with what's in your import file unless there is a 
config parameter that keeps it from doing that.  I'm not aware of anything like 
that but am not intimately familiar with all the config options.

I'd be curious to know if it would simply create 4 NEW records for you.  A "+" 
in the id column will cause new items to be created, and you'd need to add a 
"collection" column.

Or change the order of the items in your import file and see if you get 
different results.  Maybe put the one with the empty dc.rights.license field 
first and see what happens.

Kelley Canon
Language & Culture Archives
REAP Administrator
SIL International


On Fri, Feb 12, 2021 at 4:29 PM Bouchard, Kerry  wrote:

Kelly,
Thanks. I would have thought that if any of the column headers were 
wrong, none of the records would import, but from what I can see the problem 
only occurs when one of the DSpace records has an empty field.
Attached is a spreadsheet with four records, where the 
dc.license.rights field in the first, second, and fourth records in DSpace have 
the value “Not blank”:
[https://groups.google.com/group/dspace-tech/attach/48e4512fae8c7/image001.png?part=0.1&view=1]

And the third record has empty data in the dc.rights.license field:
[https://groups.google.com/group/dspace-tech/attach/48e4512fae8c7/image002.png?part=0.2&view=1]
When I try to import the CSV file, it sees the changes on the first 
and second record, but not the next two:
[https://groups.google.com/group/dspace-tech/attach/48e4512fae8c7/image003.png?part=0.3&view=1]
After that it just stops and doesn’t recognize that changes have 
been made in the two remaining spreadsheet records.

Thanks, Kerry

From: Kelley Canon 
Sent: Wednesday, February 10, 2021 2:19 PM
To: Bouchard, Kerry 
Cc: dspac...@googlegroups.com
Subject: Re: [dspace-tech] Metadata Import of CSV file stops when a field in 
the CSV file with new data matches a record where the corresponding field in 
the DSpace record contains blank/null data

Hi Kerry -

I would recommend first looking at the column headers in row 1 of your CSV 
file.  Is ID the first column header in column A?  Is any column missing a 
valid metadata element name?  Do you perhaps have one or more blank columns 
included after your metadata columns, to the right of your data?

If I'm understanding correctly what you describe in your first bullet point, I 
think dSpace will simply overwrite the null data with the new data inc

Re: [dspace-tech] Metadata Import of CSV file stops when a field in the CSV file with new data matches a record where the corresponding field in the DSpace record contains blank/null data

[Sean Kalynuk]

Hi Kerry,

Are you only importing the CSV file from the user interface? I wonder what 
would happen if you tried importing the metadata using the command-line tool. 
Since it’s the same core code that’s used, I’m guessing that the merge logic 
won’t be any different, but the method for transferring the CSV file to the 
server via the user interface is different than if you transferred the file 
yourself and used the command-line tool.

For your earlier tests with debugging turned on, see if there are lines in the 
log files that have the keyword metadata_import. (Note that I’m basing this on 
my knowledge of DSpace 6.3. If you have a much older version, the log entries 
might be different.) That information might give you a clue as to what is going 
on.

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Kelley Canon 
Date: Monday, February 15, 2021 at 8:42 AM
To: Bouchard, Kerry 
Cc: dspace-tech@googlegroups.com 
Subject: Re: [dspace-tech] Metadata Import of CSV file stops when a field in 
the CSV file with new data matches a record where the corresponding field in 
the DSpace record contains blank/null data
Caution: This message was sent from outside the University of Manitoba.
Kerry -

I looked at your data and I don't see any problems.  dSpace should just 
overwrite the empty field with what's in your import file unless there is a 
config parameter that keeps it from doing that.  I'm not aware of anything like 
that but am not intimately familiar with all the config options.

I'd be curious to know if it would simply create 4 NEW records for you.  A "+" 
in the id column will cause new items to be created, and you'd need to add a 
"collection" column.

Or change the order of the items in your import file and see if you get 
different results.  Maybe put the one with the empty dc.rights.license field 
first and see what happens.

Kelley Canon
Language & Culture Archives
REAP Administrator
SIL International


On Fri, Feb 12, 2021 at 4:29 PM Bouchard, Kerry 
mailto:k.bouch...@tcu.edu>> wrote:

Kelly,
Thanks. I would have thought that if any of the column headers were 
wrong, none of the records would import, but from what I can see the problem 
only occurs when one of the DSpace records has an empty field.
Attached is a spreadsheet with four records, where the 
dc.license.rights field in the first, second, and fourth records in DSpace have 
the value “Not blank”:
[cid:image001.png@01D70519.B510B010]

And the third record has empty data in the dc.rights.license field:
[cid:image002.png@01D70519.B510B010]
When I try to import the CSV file, it sees the changes on the first 
and second record, but not the next two:
[cid:image003.png@01D70519.B510B010]
After that it just stops and doesn’t recognize that changes have 
been made in the two remaining spreadsheet records.

Thanks, Kerry

From: Kelley Canon mailto:kelley_ca...@sil.org>>
Sent: Wednesday, February 10, 2021 2:19 PM
To: Bouchard, Kerry mailto:k.bouch...@tcu.edu>>
Cc: dspace-tech@googlegroups.com
Subject: Re: [dspace-tech] Metadata Import of CSV file stops when a field in 
the CSV file with new data matches a record where the corresponding field in 
the DSpace record contains blank/null data

Hi Kerry -

I would recommend first looking at the column headers in row 1 of your CSV 
file.  Is ID the first column header in column A?  Is any column missing a 
valid metadata element name?  Do you perhaps have one or more blank columns 
included after your metadata columns, to the right of your data?

If I'm understanding correctly what you describe in your first bullet point, I 
think dSpace will simply overwrite the null data with the new data included in 
your CSV.  Feel free to attach a sample if you're not able to resolve these 
issues.

>From down the road in Dallas,
Kelley Canon
Language & Culture Archives
REAP Administrator
SIL International


On Wed, Feb 10, 2021 at 1:40 PM Bouchard, Kerry 
mailto:k.bouch...@tcu.edu>> wrote:

We’ve been having problems with the Metadata Import function sometimes either 
stopping after a few records or sending a “No changes detected” message. I 
think I’ve narrowed the problem to the following circumstance:

• One or more records in the CSV file being imported contains a new 
value for a field that in the existing DSpace metadata record is present, but 
contains a blank/null value.

• For that record, the new value in the corresponding CSV file is the 
only field that has a changed value.

• If the record is the first row in the CSV file, we will then get a 
“No changes detected” message. If it occurs further down in the file, the 
records above will process correctly, but then processing stops with the 
problem row.
If the metadata field doesn’t exist in the DSpace record at all, then there’s 
not a problem – the import will show that it is Adding the new f

Re: [dspace-tech] Google Analytics leads to connection pool exhausted?

[Sean Kalynuk]

Hi Gabriela,

Some options to try:

  1.  See if the connection limit on the PostgreSQL side is too low. This could 
be system-wide, for the database, or even for the DSpace database user.
  2.  Increase db.maxconnections in your DSpace configuration and restart 
Tomcat. My understanding though is that, without a global connection pool, this 
setting applies per webapp, so increasing it can run the risk of hitting the 
connection limit to the PostgreSQL database even faster since each webapp can 
now allocate up to db.maxconnections. However, you might find that increasing 
it alleviates your immediate problem. If you do increase it, make sure your 
database can handle the increased connections as per option 1.
  3.  Configure a global connection pool for all of Tomcat to be shared by all 
DSpace webapps. There’s a discussion thread with details 
here.

Some other reference information:

https://wiki.lyrasis.org/display/DSDOC5x/Configuration+Reference#ConfigurationReference-DSpaceDatabaseConfiguration

https://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html

Although it’s for DSpace 6.x, the install guide has a section called “External 
Database Connection Pool” here: 
https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-Externaldatabaseconnectionpool
I don’t think the DSpace 5.x manual has this information.

--
Sean

From: dspace-tech@googlegroups.com 
Date: Wednesday, January 13, 2021 at 11:05 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Google Analytics leads to connection pool exhausted?
Caution: This message was sent from outside the University of Manitoba.

I have been running DSpace 5.5 with Tomcat 7 and Postgresql 9 in production for 
more than five years. A few weeks ago, the site started displaying Internal 
Server Error. The errors were coming up quite often, every couple of hours or 
so, and were going away after a tomcat restart. The logs were showing "Cannot 
get a connection, pool error Timeout waiting for idle object". I enabled the 
DEBUG level for logging, and every time before the connection pool was 
exhausted, I noticed this in the logs:



2021-01-13 03:36:34,379 DEBUG org.dspace.google.GoogleRecorderEventListener @ 
Usage event received bitstream:view

2021-01-13 03:36:34,380 DEBUG org.apache.http.client.protocol.RequestAddCookies 
@ CookieSpec selected: best-match

2021-01-13 03:36:34,380 DEBUG org.apache.http.client.protocol.RequestAuthCache 
@ Auth cache not set in the context

2021-01-13 03:36:34,380 DEBUG 
org.apache.http.impl.conn.PoolingHttpClientConnectionManager @ Connection 
request: [route: {s}->https://www.google-analytics.com:443][total kept alive: 
0; route allocated: 2 of 2; total allocated: 2 of 20]

2021-01-13 03:36:41,422 ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL 
connection Error -

2021-01-13 03:36:41,423 WARN org.dspace.app.webui.servlet.DSpaceServlet @ 
anonymous:no_context:database_error:org.apache.commons.dbcp.SQLNestedException\colon;
 Cannot get a connection, pool error Timeout waiting for idle object



Any help would be much appreciated,

Gabriela
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/d654dc18-490b-41b8-8c0d-0a32a80de6e4n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB0848915BB0C9D4B3FF6A9DB6E8A90%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] How can I expose ORCID in XMLUI

[Sean Kalynuk]

Hi Nason,

You might want to check out this:

https://www.atmire.com/articles/detail/new-features-for-dspace-5-and-6-orcid-integration
https://atmire.github.io/expanded-ORCID-support/#/

I have implemented it in our dev environment and the ORCID icon is displayed 
with each author and links to their ORCID profile. There are other features in 
the patch as well, such as searching for ORCID ID. If you do decide to try the 
patch, please also review these issues:

https://github.com/atmire/expanded-ORCID-support/issues/3
https://jira.lyrasis.org/browse/DS-3999

When mixing these patches, the expanded ORCID support will override the fix for 
DS-3999.

--
Sean

From: dspace-tech@googlegroups.com 
Date: Friday, November 6, 2020 at 2:27 PM
To: DSpace Technical Support 
Subject: [dspace-tech] How can I expose ORCID in XMLUI
Caution: This message was sent from outside the University of Manitoba.
I want to grab ORCID and use it my item display template.

I found 
http://dspace.2283337.n4.nabble.com/exposing-author-s-ORCID-in-simple-item-view-td4685628.html
 and points to code at 
https://github.com/stfc/DSpace/commit/50c90c504463e0a9067797cbb7e3e8a77c75c2ca 
which I followed but the value @orcid_id is always blank even if I have an 
ORCID present in the record as I can see it in the metadata edit.

Has anyone managed to figure out this. I am using DSpace 6.3 and I have enabled 
ORCID integration.

Regards
Nason
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/226ac8ba-2349-41c1-a028-579b18447fe1n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTOPR0101MB2251E51E9653ED35BA20E115E8ED0%40YTOPR0101MB2251.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Re: dspace metadata fields

[Sean Kalynuk]

Hey everyone,

Some issues to be aware of regarding the metadata language value:

https://jira.lyrasis.org/browse/DS-2174
https://jira.lyrasis.org/browse/DS-2548
https://jira.lyrasis.org/browse/DS-4169
https://jira.lyrasis.org/browse/DS-4493

And some other info:

https://wiki.lyrasis.org/display/DSPACE/TechnicalFAQ#TechnicalFAQ-MetadatavaluesinCSVexportseemtohaveduplicatecolumns

I agree with David that using OpenRefine on exported metadata cleanup is a 
great option. You’ll just have to be aware of the issues where a “null” 
language (e.g., dc.contributor.advisor) versus an “empty” language (e.g., 
dc.contributor.advisor[]) will be updated differently later on depending on 
where in DSpace the change is being made. Specifically, DS-4169 (fixed in 
DSpace 6.4) describes the issue whereby “null” language values get changed to 
“empty” language values when editing metadata via the user interface. So, I 
think that having a language qualifier (e.g., en or en_US) would eliminate the 
uncertainty with subsequent metadata updates (at least until all the issues are 
resolved).

--
Sean

From: dspace-tech@googlegroups.com 
Date: Thursday, October 29, 2020 at 10:23 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: dspace metadata fields
Caution: This message was sent from outside the University of Manitoba.
I think you could export the metadata into OpenRefine of even LibreOffice Calc. 
Then trim the leading and ending white spaces and compact any consecutive white 
spaces. Then address the language qualifier. If everything is in English you 
could set that column to [en] or you could just empty the column. You will have 
to make changes to you metadata scheme in DSpace to keep this from reoccurring. 
Once your data is clean, import and overwrite.

David Bigwood
dbigw...@lpi.usra.edu
Library, Planetary Image Facility
Lunar and Planetary Institute

On Thursday, October 29, 2020 at 2:15:49 AM UTC-5 sunit...@gmail.com wrote:
Dear all

Our metadata in dspace is scattered under different following metadata fields.

How can we club together such data in one go.

dc.contributor.advisor
dc.contributor.advisor[]
dc.contributor.advisor[en_US]
dc.contributor.author
dc.contributor.author[]
dc.contributor.author[en]
dc.contributor.author[en_US]
dc.date.accessioned
dc.date.accesioned[]
dc.date.accessioned[en_US]
dc.date.available...

reg

Sunita Barve

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/d6aa10e9-8a73-4739-9806-7ebfe93fd2b9n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTOPR0101MB2251CB133B530C245F9B24B9E8140%40YTOPR0101MB2251.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Re: Dspace 6.3 LDAP authenticate issue

[Sean Kalynuk]

You have authentication-ld.id_field instead of authentication-ldap.id_field

--
Sean

From:  on behalf of "lon...@gmail.com" 

Date: Monday, September 28, 2020 at 2:42 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: Dspace 6.3 LDAP authenticate issue

Caution: This message was sent from outside the University of Manitoba.

Hi Sean,
Thanks for your replied. I just double checked in my  LDAP configure file and I 
do have the correct information for "authentication-ld.id_field"
Here is my LDap configuration file.

authentication-ldap.enable = true
authentication-ldap.autoregister = true
authentication-ldap.provider_url = ldap://xx.xxx.x.x/
authentication-ld.id_field = 
authentication-ldap.object_context = dc=aaa\,bb=c\,dc=ca
authentication-ldap.search_context = dc=aaa\,bb=c\,dc=ca
authentication-ldap.email_field = mail
authentication-ldap.surname_field = sn
authentication-ldap.givenname_field = givenName
authentication-ldap.login.specialgroup = group-name
authentication-ldap.search_scope = 2
authentication-ldap.search.user = cn=xxx\,cn=\,dc=\,dc=\,dc=ca
authentication-ldap.search.password = 12345

Any thought?



On Sunday, September 27, 2020 at 9:32:07 PM UTC-5 lon...@gmail.com wrote:
hi All,
I got dspace 6.3 setup and I'm planning to use LDAP as a part of the login.
However, when I tried to login I got this error message.
I hope someone can give me a hint to make it works .
thanks
LN
==
Java stacktrace: java.lang.NullPointerException at 
javax.naming.directory.BasicAttributes.put(BasicAttributes.java:183) at 
org.dspace.authenticate.LDAPAuthentication$SpeakerToLDAP.getDNOfUser(LDAPAuthentication.java:498)
 at 
org.dspace.authenticate.LDAPAuthentication.authenticate(LDAPAuthentication.java:232)
 at 
org.dspace.authenticate.AuthenticationServiceImpl.authenticateInternal(AuthenticationServiceImpl.java:111)
 at 
org.dspace.authenticate.AuthenticationServiceImpl.authenticate(AuthenticationServiceImpl.java:81)
 at 
org.dspace.app.xmlui.utils.AuthenticationUtil.authenticate(AuthenticationUtil.java:120)
 at 
org.dspace.app.xmlui.aspect.eperson.LDAPAuthenticateAction.act(LDAPAuthenticateAction.java:84)
 at 
org.apache.cocoon.sitemap.impl.DefaultExecutor.invokeAction(DefaultExecutor.java:55)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.ActTypeNode.invoke(ActTypeNode.java:105)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
 at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239)
 at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:186)
 at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(TreeProcessor.java:260)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:107)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:87)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
 at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239)
 at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:186)
 at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(TreeProcessor.java:260)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:107)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
 at 

Re: [dspace-tech] Dspace 6.3 LDAP authenticate issue

[Sean Kalynuk]

Looks to me like you don’t have authentication-ldap.id_field defined.

Probably best to review the full configuration instructions at 
https://wiki.lyrasis.org/display/DSDOC6x/Authentication+Plugins#AuthenticationPlugins-LDAPAuthentication

--
Sean

From:  on behalf of "lon...@gmail.com" 

Date: Sunday, September 27, 2020 at 9:32 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Dspace 6.3 LDAP authenticate issue

Caution: This message was sent from outside the University of Manitoba.

hi All,
I got dspace 6.3 setup and I'm planning to use LDAP as a part of the login.
However, when I tried to login I got this error message.
I hope someone can give me a hint to make it works .
thanks
LN
==
Java stacktrace: java.lang.NullPointerException at 
javax.naming.directory.BasicAttributes.put(BasicAttributes.java:183) at 
org.dspace.authenticate.LDAPAuthentication$SpeakerToLDAP.getDNOfUser(LDAPAuthentication.java:498)
 at 
org.dspace.authenticate.LDAPAuthentication.authenticate(LDAPAuthentication.java:232)
 at 
org.dspace.authenticate.AuthenticationServiceImpl.authenticateInternal(AuthenticationServiceImpl.java:111)
 at 
org.dspace.authenticate.AuthenticationServiceImpl.authenticate(AuthenticationServiceImpl.java:81)
 at 
org.dspace.app.xmlui.utils.AuthenticationUtil.authenticate(AuthenticationUtil.java:120)
 at 
org.dspace.app.xmlui.aspect.eperson.LDAPAuthenticateAction.act(LDAPAuthenticateAction.java:84)
 at 
org.apache.cocoon.sitemap.impl.DefaultExecutor.invokeAction(DefaultExecutor.java:55)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.ActTypeNode.invoke(ActTypeNode.java:105)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
 at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239)
 at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:186)
 at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(TreeProcessor.java:260)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:107)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:87)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
 at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239)
 at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:186)
 at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(TreeProcessor.java:260)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:107)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
 at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239)
 at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:186)
 at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.buil

Re: [dspace-tech] Hiding Files/Bitsteams from regular users

[Sean Kalynuk]

Hi Marc,

We are using DSpace 6.3 (non-CRIS) and when bitstream READ authorizations (aka 
resource policies) are *not* set for any user/group (especially Anonymous!), 
then only full DSpace administrators can see/manage the bitstream.

--
Sean

From:  on behalf of "brouar...@gmail.com" 

Date: Saturday, August 15, 2020 at 8:12 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Hiding Files/Bitsteams from regular users

Caution: This message was sent from outside the University of Manitoba.

Dear List,

Is it poossible to hide a particular file/bitstream from anybody but the 
administrators, whilst still having the rest of the item visible. I know you 
can set read permissions on the bitstream but this still makes it visible and 
as we have request a copy setup, this usesr would see this instead of the 
download.

We currently have DSPACE CRIS 5.10, but I think this is also applicable to non 
cris versions. I have looked in the documentation and done the usual googling, 
but can not seem to find a way of achieving our goal. A point in the right 
direction would be greatly appreciated

kind regards
Marc
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/5c10ea47-cd9a-4ed7-8b62-8070272a1c73n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/AAF2B4E0-A08B-47AB-86FF-CF857A40F251%40umanitoba.ca.

Re: [dspace-tech] OAI harvesting

[Sean Kalynuk]

Hi Marcia,

It’s best if you get a system administrator to schedule a daily cron task on 
that server:

https://wiki.lyrasis.org/display/DSDOC6x/OAI#OAI-OAI-PMHServerMaintenance

I don’t know how to initiate it from the user interface.

--
Sean

From:  on behalf of DCUOIT 
Date: Tuesday, June 23, 2020 at 11:28 AM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] OAI harvesting

Caution: This message was sent from outside the University of Manitoba.


Thanks, Sean. Is there any other way to do it? I dont have access to the server 
so I cant really run commands.

Marcia

On Tuesday, June 23, 2020 at 11:31:48 AM UTC-4, Sean Kalynuk wrote:
Hi Marcia,

Run “dspace oai import” from the command-line (as the DSpace software owner) to 
update the records used by OAI.

After that run “dspace oai clean-cache” just to be sure the cache is cleared.

--
Sean

From: > on behalf of DCUOIT 
>
Date: Tuesday, June 23, 2020 at 10:15 AM
To: DSpace Technical Support >
Subject: [dspace-tech] OAI harvesting

Caution: This message was sent from outside the University of Manitoba.


Hi there,

I am somewhat new to the application. We currently have harvesting setup for 
our repository using oai_etdms and received an error report from the 
organization harvesting the records, where there were spaces in the file name. 
I was asked to update the metadata and I did; but when the harvest was run 
again, the link in the record was not updated so the space is still appearing. 
I need some assistance in figuring out what I am supposed to change so that the 
bitstream URL is correct. Here is an example of a 
record:https://ir.library.dc-uoit.ca/dspace-oai/request?verb=ListRecords&resumptionToken=MTo3MDB8Mjpjb2xfMTAxNTVfNXwzOnw0Onw1Om9haV9kYw==.
 I am hoping that someone can assist me as I am unclear how to do that. The 
only other alternative that I can logically think of is the delete the existing 
entry and recreate the record. I would prefer not to do that because there are 
more than 100 records.

Thank you,
Marcia
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspac...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/c9c3e4d6-d516-46f3-83ec-89b7cccffe9eo%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/c9c3e4d6-d516-46f3-83ec-89b7cccffe9eo%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/6c9a997e-8a8d-41d9-a612-4b91cfb5afa5o%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/6c9a997e-8a8d-41d9-a612-4b91cfb5afa5o%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/7843F3BF-426C-46B8-8517-C938230CA4F0%40umanitoba.ca.

Re: [dspace-tech] OAI harvesting

[Sean Kalynuk]

Hi Marcia,

Run “dspace oai import” from the command-line (as the DSpace software owner) to 
update the records used by OAI.

After that run “dspace oai clean-cache” just to be sure the cache is cleared.

--
Sean

From:  on behalf of DCUOIT 
Date: Tuesday, June 23, 2020 at 10:15 AM
To: DSpace Technical Support 
Subject: [dspace-tech] OAI harvesting

Caution: This message was sent from outside the University of Manitoba.


Hi there,

I am somewhat new to the application. We currently have harvesting setup for 
our repository using oai_etdms and received an error report from the 
organization harvesting the records, where there were spaces in the file name. 
I was asked to update the metadata and I did; but when the harvest was run 
again, the link in the record was not updated so the space is still appearing. 
I need some assistance in figuring out what I am supposed to change so that the 
bitstream URL is correct. Here is an example of a 
record:https://ir.library.dc-uoit.ca/dspace-oai/request?verb=ListRecords&resumptionToken=MTo3MDB8Mjpjb2xfMTAxNTVfNXwzOnw0Onw1Om9haV9kYw==.
 I am hoping that someone can assist me as I am unclear how to do that. The 
only other alternative that I can logically think of is the delete the existing 
entry and recreate the record. I would prefer not to do that because there are 
more than 100 records.

Thank you,
Marcia
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/c9c3e4d6-d516-46f3-83ec-89b7cccffe9eo%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/B84260D1-C7D1-491A-A818-70C69C8CA473%40umanitoba.ca.

Re: [dspace-tech] Cannot Delete Group Members/Subgroups from Groups in dspace v6.3

[Sean Kalynuk]

Here is a SQL query I've used for examining the group hierarchy. It is fixed to 
5 levels since we don't have much nesting in our system.

select
epg1.eperson_group_id as GID1,
epg1.name as Name1,
epg2.eperson_group_id as GID2,
epg2.name as Name2,
epg3.eperson_group_id as GID3,
epg3.name as Name3,
epg4.eperson_group_id as GID4,
epg4.name as Name4,
epg5.eperson_group_id as GID5,
epg5.name as Name5
from epersongroup epg1
left join group2group g2g1 on g2g1.parent_id=epg1.uuid
left join epersongroup epg2 on epg2.uuid=g2g1.child_id
left join group2group g2g2 on g2g2.parent_id=epg2.uuid
left join epersongroup epg3 on epg3.uuid=g2g2.child_id
left join group2group g2g3 on g2g3.parent_id=epg3.uuid
left join epersongroup epg4 on epg4.uuid=g2g3.child_id
left join group2group g2g4 on g2g4.parent_id=epg4.uuid
left join epersongroup epg5 on epg5.uuid=g2g4.child_id
order by Name1,Name2,Name3,Name4,Name5

--
Sean

On 2020-06-19, 9:48 AM, "Mark H. Wood,UL 0115A,+1 317 274 0749, on behalf of 
Mark H. Wood"  wrote:

The seemingly endless recursion (which caused the stack overflow)
makes me think that there may be a circular group membership
somewhere.  Group A contains group B contains group A would be a
simple example.  The only way I've thought of to look for such a
problem is to inspect the group2group database table.  The content of
that table should represent a collection of directed acyclic graphs.
If one of those graphs is cyclic, GroupServiceImpl.getChildren will
never terminate and will eventually fill the stack.

I don't have a simple, quick way to find such a cycle, but I found a
few references that will probably tell you more than you ever wanted
to know about the subject, with suggestions for practical solutions.


https://stackoverflow.com/questions/261573/best-algorithm-for-detecting-cycles-in-a-directed-graph
https://www.geeksforgeeks.org/detect-cycle-in-a-graph/
https://en.wikipedia.org/wiki/Cycle_(graph_theory)

I'd read the one at StackOverflow first.  Remember that the table
probably contains *more than one graph*.  The 'epersongroup' table
contains all of the groups and may be helpful for inspecting the whole
collection of graphs.



There's another approach:  add some code to limit the depth of
getChildren, throwing an exception when the limit is hit.  Catching,
logging and then re-throwing the exception in getChildren ought to
show you the problematic path.  This would be similar to the depth-first
search for a cycle suggested in the references above.  I don't know
which way would be better for you.

We probably ought to have such an (adjustable) depth limit in
getChildren anyway.

-- 
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/20200619144824.GB14311%40IUPUI.Edu.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/35D16822-A01C-4F13-B7B2-042D4E0AD169%40umanitoba.ca.

Re: [dspace-tech] “Item_to_Bitstream” table

[Sean Kalynuk]

Hi Kelley,

You can join item to bundle via “item2bundle” and then join bundle to bitstream 
via “bundle2bitstream”.

--
Sean

From:  on behalf of Kelley Canon 

Date: Monday, June 15, 2020 at 1:44 PM
To: DSpace Technical Support 
Subject: [dspace-tech] “Item_to_Bitstream” table

Caution: This message was sent from outside the University of Manitoba.


Dear colleagues -

Is there a table in dSpace 6.3 that is comparable to the “Item_to_Bitstream” 
table which we had in DSpace 4.x?

Or is there some method I'm not aware of in dSpace 6.3 to obtain a list of 
bitstreams associate with items?  I use "Export Metadata" frequently but 
sometimes need to know the bitstream filenames associated with each item.

Thank you,
Kelley Canon
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/ca5503e4-a7c8-49f2-bf92-7bd2b1b77e14o%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/319D3B7F-26BA-4D4F-8D11-4198165B04A4%40umanitoba.ca.

Re: [dspace-tech] DSpace and AI / Dspace com IA

[Sean Kalynuk]

Hi Matheus,

Coincidentally, I am currently trying out fastText (https://fasttext.cc/) to 
help with document classification. Unfortunately I haven’t integrated anything 
with DSpace itself just yet since I’m only generating CSV metadata that will be 
applied using the DSpace metadata import feature.

--
Sean

From:  on behalf of Matheus Otoni 

Date: Wednesday, June 10, 2020 at 3:23 PM
To: DSpace Technical Support 
Subject: [dspace-tech] DSpace and AI / Dspace com IA

Caution: This message was sent from outside the University of Manitoba.


 Hi all, how are you?

I am studying artificial intelligence and would like to know if anyone has done 
already anything with dspace using AI.

Thank you!
BR,
Matheus Otoni



Olá pessoal, tudo bem?

Estou estudando inteligência artificial e gostaria de saber se alguém já fez 
alguma coisa com o dspace usando IA.

Obrigado!
Att,
Matheus Otoni
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/41ddf914-81d3-4d2c-8c4a-4da1d6d1f905o%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/9E3EE27C-A648-4F0D-8DE2-1B32042D82AC%40umanitoba.ca.

Re: [dspace-tech] Re: Dspace 6.3 Author Solr Metadata?

[Sean Kalynuk]

I think you’ll find more information on this issue here:

https://jira.lyrasis.org/browse/DS-2852

--
Sean

From: 'Muhammad Yousaf' via DSpace Technical Support 

Reply-To: Muhammad Yousaf 
Date: Wednesday, May 13, 2020 at 2:55 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: Dspace 6.3 Author Solr Metadata?

Caution: This message was sent from outside the University of Manitoba.


Anyone with a solution?

On Thursday, April 30, 2020 at 4:53:37 AM UTC+4, Muhammad Yousaf wrote:
Dear Everyone,

I just noticed that the authors under the "Discover" sidebar are showing in a 
long random string instead of actual names. Is it the metadata which is 
showing? I believe it is somehow related to Solr index-discovery but any idea 
what happened suddenly?

I was working on Orcid integration using Atmire patch but that didn't work 
instead this happened. Anyone knows how to fix it? or somehow revert back?

Thanks in Advance.

[https://groups.google.com/group/dspace-tech/attach/4d504aee9ca5b/Auto%20Generated%20Inline%20Image%201?part=0.1&view=1&authuser=0]

[https://groups.google.com/group/dspace-tech/attach/4d504aee9ca5b/Auto%20Generated%20Inline%20Image%202?part=0.2&view=1&authuser=0]
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/05a70ce9-d345-48ec-a964-e78bf1f2842c%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CADADD4C-5DC0-4010-9CF9-04D0575C2011%40umanitoba.ca.

RE: [dspace-tech] downloading vs rendering file

[Sean Kalynuk]

Hi Jose,

https://wiki.lyrasis.org/display/DSDOC6x/Configuration+Reference#ConfigurationReference-ContentInlineDispositionThreshold

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
Jose Blanco
Sent: February 5, 2020 3:28 PM
To: DSpace Technical Support 
Subject: [dspace-tech] downloading vs rendering file

I believe that when I open pdf files that are quite large, 10MB for example, 
the file is downloaded, but when the file is not so large it is rendered in 
place in the browser.  Where is this configured?

Thank you!
-Jose
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-u_49BgGZhDot8KRVtyHfa4jL__HPX8cAgQEdg8zGXsfw%40mail.gmail.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/d0ae6caa609445ef82325a387431c737%40umanitoba.ca.

RE: [dspace-tech] Upload limit problem in DSpace

[Sean Kalynuk]

Hi George,

There is also org.apache.cocoon.uploads.maxsize in 
$DSPACE_HOME/webapps/xmlui/WEB-INF/cocoon/properties/core.properties although I 
don’t know if one overrides the other. The documentation in the file seems to 
indicate there’s a 2GB limit with Cocoon, so I’m not sure how someone could 
upload something larger through the web interface.

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
George Kozak
Sent: November 12, 2019 1:49 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Upload limit problem in DSpace

Hello:
We are using DSpace 6.3, XMLUI (modified Mirage 2 theme).  In my local.cfg, I 
have the following parameter set:
upload.max = 5368709120
To set our upload max to 5GB.
However, we recently discovered that people are uploading files greater than 
5GB.
Is there another setting for uploads that I am missing?

--
***
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
g...@cornell.edu
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAB8VfOAX%2BhHHLtHtgoOdF2UV8G5r_8_5F9pS9Hh%2B1nFuWOO0jg%40mail.gmail.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/7257294d20d4493a8d2fd34939901cac%40umanitoba.ca.

RE: [dspace-tech] OAI Logging

[Sean Kalynuk]

Hi Paul,

If you have Tomcat access logging enabled, then you can search those logs for 
access to the /oai/request path.

--
Sean

-Original Message-
From: dspace-tech@googlegroups.com  On Behalf Of 
Paul Münch
Sent: November 11, 2019 2:45 AM
To: dspace-tech@googlegroups.com
Subject: [dspace-tech] OAI Logging

Hello everybody,

is there something like a OAI-Log, where we can check at what time or on what 
date our DSpace was harvested? I looked into the dspace logs and the 
'[dspace-dir]/var/oai/request' directory but didn't find what we are looking 
for.

Thank you in advance and kind regards,

Paul Münch

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/76807727-91b2-ec83-5d3c-3645cf241742%40staff.uni-marburg.de.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/e8ee792e1081402db9ef83ca3d105dd3%40umanitoba.ca.

RE: [dspace-tech] Function of Field Qualifiers (dc.fieldname[en], dc.fieldname[], etc.)

[Sean Kalynuk]

Hi Gabe,

You can find some information on the different types of column headers for the 
metadata CSV export here:

https://wiki.duraspace.org/display/DSPACE/TechnicalFAQ#TechnicalFAQ-MetadatavaluesinCSVexportseemtohaveduplicatecolumns

--
Sean


From: dspace-tech@googlegroups.com  On Behalf Of 
Gabriel Galson
Sent: May 24, 2019 12:22 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Function of Field Qualifiers (dc.fieldname[en], 
dc.fieldname[], etc.)

Group-

We're populating an XMLUI DSpace instance with test data in preparation for its 
launch.  I'm exporting metadata from a collection containing a mix of items.  
Certain fields' contents are, when viewed in the sheet exported, followed by a 
range of bracketed qualifiers.

We have...

dc.description.abstract
and
dc.description.abstract[]

also...

dc.publisher[]
and
dc.publisher[en_US]

We also have...

dc.description.provenance[en]

My questions are,
1)  On this documentation page 
 on localization 
it states "Metadata localization: DSpace associates each metadata field value 
with a language code (though it may be left empty, e.g. for numeric values)."  
Is this the process governing the creation of these bracketed values?  Is there 
a more robust description of how this works?
2)  How are they assigned per-field?  Through a configuration (if so, which)?   
Based on the field's contents?
3)  The essential question: why are we getting different versions of the same 
field?  Note that some items were ingested through SWORD, while others were 
manually uploaded, or Bulk uploaded in Simple Archive Format.
4)  In terms of bulk 
editing
 through the UI via CSV, can values in, say, dc.publisher[] and 
dc.publisher[en_US], be left in separate columns for reupload, or must they be 
consolidated?
5) is there a way to prevent these bracketed values from being 
assigned/created?  Having divergent versions of the same field in the edit 
metadata CSV complicates our metadata administration workflows.

Thank for for any insight you can provide!

-Gabe

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/f4b84d1b-fee4-4821-947e-3e6e54b0a9e2%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/d2a2dac117d740a3abc3d85c0c8d48a3%40umanitoba.ca.

RE: [dspace-tech] Setting up RDF for Dspace 6

[Sean Kalynuk]

Ashim, the URLs for (b), (c), and (d) that you listed below require appropriate 
query parameters to get sensible results.

With curl, you can test the /dspace/sparql endpoint with something like:

curl -XPOST -d 'query=select ?s ?p ?o where { ?s ?p ?o . } limit 10' 
localhost:3030/dspace/sparql

>From those results, you can take one of the “subject” URLs identified by “s”, 
>and feed it into the /dspace/get endpoint to get the graph:

curl -XGET 'http://localhost:3030/dspace/get?graph=YourURLGoesHere'

You can also query the graph names by doing something like this (limited to 10 
results):

curl -XPOST -d 'query=select ?g where { GRAPH ?g { } } limit 10' 
localhost:3030/dspace/sparql

If you get valid responses for all of these, then it would appear that your 
Fuseki server is working fine.

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
Terry Brady
Sent: March 18, 2019 1:31 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] Setting up RDF for Dspace 6

I have not run the DSpace RDF service in production.  I have tested it in 
Docker.

The following instructions will allow you to spin up a test RDF instance in 
Docker.

https://github.com/DSpace-Labs/DSpace-Docker-Images/blob/master/docker-compose-files/dspace-compose/ComposeFiles.md#add-the-rdf-service-dspace6-and-dspace7

Perhaps this will help with your troubleshooting.

Terry

On Sat, Mar 16, 2019 at 2:25 AM Ashim Kapoor 
mailto:ashim.kap...@nipfp.org.in>> wrote:
Dear All,

Here is what I did post doing the basic  downloading / configuring /installing 
DSPACE 6 on Debian 9.

1. Downloaded and unzipped apache-jena-fuseki to a directory.
2. cd to that directory
3. ./fuseki-server --localhost --config 
[dspace-install-directory]/config/modules/rdf fuseki-assembler.ttl
4. cd [dspace-install]/bin/
5. ./dspace rdfizer -convert-all

On this page :
https://wiki.duraspace.org/display/DSDOC6x/Linked+(Open)+Data
it says :

a. http://localhost:3030/ you can connect to the Fuseki Web UI.
b. http://localhost:3030/dspace/data addresses a writeable SPARQL 1.1 HTTP 
Graph Store Protocol endpoint,
c. http://localhost:3030/dspace/get a read-only one.
d. http://localhost:3030/dspace/sparql a read-only SPARQL 1.1 Query Language 
endpoint can be found.

For me ONLY (a) is working. b/c/d respond with download a text file. When I do 
b,c,d, followed by a / it says Error 404 not found.

Can someone point me in the right direction ?
Best,
Ashim



--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


--
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://github.com/terrywbrady/info
425-298-5498 (Seattle, WA)
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-tech] Re: Problems with Author LookUp functionality Dspace 6.3

[Sean Kalynuk]

Hi Kev,

Although I haven’t changed our default from “ambiguous”, you could set it to 
“unset” which is the lowest value at -1. That should get everything. After the 
first run of “dspace index-authority” all confidence values will be “unset”. As 
you update metadata from the user interface, you might see “novalue” or 
“accepted”. I have yet to see any other confidence value other than when I 
tried setting them via the “Import Metadata” feature or directly in the 
database with a SQL update. And, as usual, you need to make sure “dspace 
index-discovery” is run afterwards.

>From the code, the possible keywords (and internal integer values) are:

accepted (600)
This authority value has been confirmed as accurate by an interactive user or 
authoritative policy

uncertain (500)
Authority value is singular and valid but has not been seen and accepted by a 
human, so its provenance is uncertain

ambiguous (400)
There are multiple matching authority values of equal validity

notfound (300)
There are no matching answers from the authority

failed (200)
The authority encountered an internal failure in trying to match the value

rejected (100)
The authority recommends this submission be rejected

novalue (0)
No reasonable confidence value is available

unset (-1)
No confidence value has been set

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
Kev Evans
Sent: March 13, 2019 10:07 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: Problems with Author LookUp functionality Dspace 6.3

Hi Sean,

Many thanks.

This makes sense with the issues I am seeing.

One question. I want to retrieve as many items as possible. I currently have 
both  authority.minconfidence and authority.minconfidence.dc.contributor.author 
parameters set to 'accepted' Is this too strict?

Cheers

Kev

On Tuesday, 12 March 2019 22:18:37 UTC, Kev Evans wrote:
Hi
I am having some issues with the Author Lookup functionality on Dspace 6.3. 
resulting in multiple ID's for the same author and inconsistent search results 
from the view items link. Mostly resulting in no results. I have turned off the 
ORCID integration to identify the issue. In fact I commented out most of the 
author lookup config to see what difference it would make.

It doesn't behave as expected as in the instructions.

Can I have some help please? The site is due to go live on Monday. Some 
indication of where I am going wrong or if this is a bug of some kind will be 
much appreciated.

Kev
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-tech] Problems with Author LookUp functionality Dspace 6.3

[Sean Kalynuk]

Hi Kev,

There are some reported issues and others I've encountered. Here's a short list 
of what I posted in another thread:
• https://jira.duraspace.org/browse/DS-3999 (apply pull request 2195 to your 
source otherwise you can lose ORCID information when running "dspace 
index-authority")
• https://jira.duraspace.org/browse/DS-4073
• https://jira.duraspace.org/browse/DS-3302
• The “Import Metadata” feature (using the “ORCID:” CSV column) doesn’t do a 
lookup of pre-existing ORCID iD records in the Solr authority index and will 
create duplicates
• UpdateAuthorities has a problem with empty dc.contributor.author metadata 
(along with other issues as reported above)

Regarding the "view items" link, the search on Author ID will only return 
results based on the authority.minconfidence and 
authority.minconfidence.dc.contributor.author parameters. (There would be other 
authority.minconfidence.* parameters if you have other metadata under authority 
control). You also need to make sure you run "dspace index-discovery" from the 
command-line to update the Solr search index when you make changes to these 
parameters.

The duplicate IDs in the lookup can be cleaned up using "dspace 
index-authority" (with pull request 2195!) assuming they are no longer being 
referenced in any metadata. If there are duplicates remaining, then you'll have 
to edit the metadata of the items that reference the duplicates so as to assign 
them all to a single authority record.

--
Sean

-Original Message-
From: dspace-tech@googlegroups.com  On Behalf Of 
Kev Evans
Sent: March 12, 2019 5:19 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Problems with Author LookUp functionality Dspace 6.3

Hi 
I am having some issues with the Author Lookup functionality on Dspace 6.3. 
resulting in multiple ID's for the same author and inconsistent search results 
from the view items link. Mostly resulting in no results. I have turned off the 
ORCID integration to identify the issue. In fact I commented out most of the 
author lookup config to see what difference it would make.

It doesn't behave as expected as in the instructions.

Can I have some help please? The site is due to go live on Monday. Some 
indication of where I am going wrong or if this is a bug of some kind will be 
much appreciated.

Kev

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Author Lookup Issue - Dspace 6.3

[Sean . Kalynuk]

After confidence values have been updated, you will have to re-run "dspace 
index-discovery" to update the Solr search index. An import part is that 
the item itself has to have its "last_modified" value updated as well for 
index-discovery to update the searchable values for the item. (This would 
happen when using normal DSpace tools, but not if you updated the 
metadatavalue table yourself.) Optionally you could choose to re-build the 
entire search index but obviously that will take a lot longer. As for 
withdrawn items, queries will generally exclude them unless you have admin 
privileges and search for withdrawn items explicitly.

On Wednesday, 6 March 2019 07:08:09 UTC-6, Kiriaki Roditi wrote:
>
> Hello, 
>
>  
>
> I am experiencing the same issue and concluded that it is somehow 
> connected to the authority confidence value. 
>
> But I cannot understand why in some cases, although the authority exists 
> and the confidence is set to ‘600’, no result comes up when I lookup for 
> the author name (authors with no ORCID ID). 
>
> I noticed that this happens for names used in items that have been 
> withdrawn from the repository. Is that the case for you?
>
>  
>
> Best regards, 
>
> Kiriaki
>
>  
>
> *From:* dspac...@googlegroups.com   > *On Behalf Of *Sean Kalynuk
> *Sent:* Tuesday, March 5, 2019 10:20 PM
> *To:* Kev Evans >; DSpace Technical 
> Support >
> *Subject:* RE: [dspace-tech] Author Lookup Issue - Dspace 6.3
>
>  
>
> Hi Kevin,
>
>  
>
> I think the lack of search results when selecting “view items” is due to 
> the authority.minconfidence (or related 
> authority.minconfidence.dc.contributor.author) parameter.
>
>  
>
> --
>
> Sean
>
>  
>
> *From:* dspac...@googlegroups.com   > *On Behalf Of *Kev Evans
> *Sent:* March 5, 2019 11:39 AM
> *To:* DSpace Technical Support >
> *Subject:* [dspace-tech] Author Lookup Issue - Dspace 6.3
>
>  
>
> Hi
>
>  
>
> I'm having some issues with the Author Lookup/ORCID Integration on DSpace 
> 6.3 
>
>  
>
> I have followed and completed the steps in 
> https://wiki.duraspace.org/display/DSDOC6x/ORCID+Integration
>
>  
>
> However when I search on an Author to add, for instance, Bloggs, Joe it 
> will return a list of results for Bloggs, Joe. where Bloggs, Joe is the 
> same Author/Submitter. Hence it is Ambiguous which one to Add and when 
> using the option to 'view items' this produces an ID, but clicking on the 
> id produces no meaningful results in the Search. 
>
>  
>
> This seems to happen on Authors with no ORCID ID. Authors with an ORCID ID 
> works OK. 
>
>  
>
> Essentially, I am expecting to see returned an Author with all items 
> associated with the Author returned in the 'view items' link. 
>
>  
>
> I can't understand why this not the case. Is there further configuration I 
> need to do to achieve this? 
>
>  
>
> HELP PLEASE
>
>  
>
> Kevin
>
> -- 
> All messages to this mailing list should adhere to the DuraSpace Code of 
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> --- 
> You received this message because you are subscribed to the Google Groups 
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to dspace-tech...@googlegroups.com .
> To post to this group, send email to dspac...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
> -- 
> All messages to this mailing list should adhere to the DuraSpace Code of 
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> --- 
> You received this message because you are subscribed to the Google Groups 
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to dspace-tech...@googlegroups.com .
> To post to this group, send email to dspac...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-tech] Author Lookup Issue - Dspace 6.3

[Sean Kalynuk]

Hi Kevin,

I think the lack of search results when selecting “view items” is due to the 
authority.minconfidence (or related 
authority.minconfidence.dc.contributor.author) parameter.

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
Kev Evans
Sent: March 5, 2019 11:39 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Author Lookup Issue - Dspace 6.3

Hi

I'm having some issues with the Author Lookup/ORCID Integration on DSpace 6.3

I have followed and completed the steps in 
https://wiki.duraspace.org/display/DSDOC6x/ORCID+Integration

However when I search on an Author to add, for instance, Bloggs, Joe it will 
return a list of results for Bloggs, Joe. where Bloggs, Joe is the same 
Author/Submitter. Hence it is Ambiguous which one to Add and when using the 
option to 'view items' this produces an ID, but clicking on the id produces no 
meaningful results in the Search.

This seems to happen on Authors with no ORCID ID. Authors with an ORCID ID 
works OK.

Essentially, I am expecting to see returned an Author with all items associated 
with the Author returned in the 'view items' link.

I can't understand why this not the case. Is there further configuration I need 
to do to achieve this?

HELP PLEASE

Kevin
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

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

[Sean Kalynuk]

We are running DSpace 6.3 and have implemented the ORCID authority feature.

However, we’ve encountered a number of issues/quirks:

· https://jira.duraspace.org/browse/DS-3999 (apply pull request 2195)

· https://jira.duraspace.org/browse/DS-4073

· https://jira.duraspace.org/browse/DS-3302

· The “Import Metadata” feature (using the “ORCID:” CSV column) doesn’t 
do a lookup of pre-existing ORCID iD records in the Solr authority index and 
will create duplicates

· UpdateAuthorities has a problem with empty dc.contributor.author 
metadata (along with other issues as reported above)

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
helix84
Sent: January 22, 2019 7:57 AM
To: tuf04...@temple.edu
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] ORCID integration and DSpace versions- will it work 
pre-6.3?

Thanks for pointing that out. Yes, you will need DSpace 5.9 or 6.3 or newer. I 
added a note on top of the documentation page.


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


On Tue, Jan 22, 2019 at 12:49 PM 
mailto:tuf04...@temple.edu>> wrote:
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 mention of 
this in the documentation so I wanted to confirm via the community.

Thank you for any insight you can provide!

-Gabe
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-tech] OAI sets not showing

[Sean Kalynuk]

Not sure what version you’re using, but there is one bug that could be related 
to your problems:

https://jira.duraspace.org/browse/DS-3733

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
Stan Orlov
Sent: January 15, 2019 2:01 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] OAI sets not showing

Wow!  If that isn't magic, I don't know what is!  I replaced Á with A, ran 
clean-cache, and voila, I can now see sets!

Thank you very much, Fazio!


On Saturday, 12 January 2019 06:14:13 UTC-4, Fazio Riccardo wrote:
Dear Stan,

I think the problem is the char itself and does not depend on its position;
Try to use "A" instead of "Á".
I think it is not necessary to reindex but  you can simply run a clean cache of 
the oai with:
[dspace.dir]/bin/dspace oai clean-cache
Hope this helps
Riccardo
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-tech] REST api

[Sean Kalynuk]

Following up... 

The POST body requires a MetadataEntry object. More information here:

DSpace 5.x:

https://wiki.duraspace.org/display/DSDOC5x/REST+API#RESTAPI-Model-Objectdatatypes

DSpace 6.x:

https://wiki.duraspace.org/display/DSDOC6x/REST+API#RESTAPI-Model-Objectdatatypes

--
Sean

-Original Message-
From: Sean Kalynuk 
Sent: December 17, 2018 1:39 PM
To: 'Jose Blanco' ; DSpace Technical Support 

Subject: RE: [dspace-tech] REST api

Hi Jose,

Looks like there's a bug in 5.1:

https://jira.duraspace.org/browse/DS-2501?src=confmacro

Also, I think the find-by-metadata-field request requires a POST instead of a 
GET. Using GET might have resulted in the 405 error.

--
Sean

-Original Message-
From: dspace-tech@googlegroups.com  On Behalf Of 
Jose Blanco
Sent: December 17, 2018 12:57 PM
To: DSpace Technical Support 
Subject: [dspace-tech] REST api

what is wrong with this request?

RESTapi/items/find-by-metadata-field?key=dc.title&value=test&language=en_US

I'm getting a 405 error.

With dspace versin 5.1

Thank you!
-Jose

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-tech] REST api

[Sean Kalynuk]

Hi Jose,

Looks like there's a bug in 5.1:

https://jira.duraspace.org/browse/DS-2501?src=confmacro

Also, I think the find-by-metadata-field request requires a POST instead of a 
GET. Using GET might have resulted in the 405 error.

--
Sean

-Original Message-
From: dspace-tech@googlegroups.com  On Behalf Of 
Jose Blanco
Sent: December 17, 2018 12:57 PM
To: DSpace Technical Support 
Subject: [dspace-tech] REST api

what is wrong with this request?

RESTapi/items/find-by-metadata-field?key=dc.title&value=test&language=en_US

I'm getting a 405 error.

With dspace versin 5.1

Thank you!
-Jose

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-tech] RESTaip listing collections

[Sean Kalynuk]

Hi Jose,

I'm using a newer version (6.3), but adding the limit option to the query 
changes the number of results. Try something like this:

RESTapi/collections?limit=1000

--
Sean

-Original Message-
From: dspace-tech@googlegroups.com  On Behalf Of 
Jose Blanco
Sent: December 10, 2018 3:45 PM
To: DSpace Technical Support 
Subject: [dspace-tech] RESTaip listing collections

why is it that when I do

RESTapi/collections/

I only see 99 collections when there are mores.  I have version 5.2.
Could someone point me to the patch that fixes this.

Thank you!
-Jose

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-tech] Re: DSpace 6.2 authority key batch import broken?

[Sean Kalynuk]

Hi,

There is a ticket for this issue:

https://jira.duraspace.org/browse/DS-3994

I have tested the suggested solution which works fine with our DSpace 6.3 
installation.

The check for the colon character as a separator is for when you import the 
authority value, such as an ORCID ID.

Example CSV column header:

ORCID:dc.contributor.author[en_US]

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
san...@sedici.unlp.edu.ar
Sent: November 6, 2018 9:33 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: DSpace 6.2 authority key batch import broken?

Hello Sean,

At our repo, https://digital.cic.gba.gob.ar/, we have the same issue as well. 
Metadata import fails to parse Authority keys.
I did some debugging and apparently the error is here: 
MetadataImport#isAuthorityControlledField()


private static boolean isAuthorityControlledField(String md)
{
  String mdf = StringUtils.substringAfter(md, ":");
  mdf = StringUtils.substringBefore(mdf, "[");
  return authorityControlled.contains(mdf);
}

The problem is in the line


  String mdf = StringUtils.substringAfter(md, ":");

That method always returns an empty String as there is no character ":"  in the 
metadata names (the CSV headers).

Has anyone an idea of the purpose of this line or the use of the character ":" 
in the metadata names?

Many Thanks,
Santi

El viernes, 23 de febrero de 2018, 14:38:27 (UTC-3), Sean Aery escribió:
Hello all,

At Duke, we are working on bringing up DSpace 6.2 and have encountered what 
appears to be a bug related to how batch metadata import handles authority (key 
& confidence) data.

Upon metadata export, we correctly see the following in a CSV for 
dc.contributor.author with authority:
Jones, Sharon::333::600

However, upon a CSV import using the same :: delimiters, the authority key and 
confidence are seemingly being ignored.

  *   adding authority key & confidence to an existing value that previously 
had none: no changes detected
  *   changing authority key or confidence on an existing value: no changes 
detected
  *   adding a new value with authority key & confidence: the string part is 
detected and written but the authority data is discarded
This happens whether using the web UI (xmlui) "Import Metadata" link or the CLI 
metadata-import command. Has anyone else experienced this? Any ideas for 
workarounds?

Many thanks,
Sean

~~
Sean Aery
Digital Projects Developer
Software Development & Integration Services
Duke University Libraries
030U Bostock Library Box 90198
Durham, NC 27708
sean...@duke.edu

~~

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-tech] XMLUI as Root DSpace 6.3

[Sean Kalynuk]

Hi Jake,

I also recommend Tim’s deployment suggestion (i.e., ROOT.xml). However, just 
make sure you do not have both a Context element in server.xml and a ROOT.xml 
file for the same webapp, otherwise you can run into the “double deployment” 
issue. When using the path attribute for the Context element in server.xml, the 
docBase should not be under the server.xml Host appBase path unless 
deployOnStartup and autoDeploy are both false.

See https://tomcat.apache.org/tomcat-8.5-doc/config/context.html for details.

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
Tim Donohue
Sent: October 31, 2018 11:21 AM
To: Cameron, Jacob 
Cc: dspace-tech@googlegroups.com
Subject: Re: [dspace-tech] XMLUI as Root DSpace 6.3

Hi Jake,

A simple Tomcat Context fragment should work.  That's all I tend to use.  So, 
for example, having a file named:

[tomcat]/conf/Catalina/localhost/ROOT.xml

All that file needs to contain is one line...something like this:



Technically, this same sort of configuration should also work in your 
server.xml, under the  section (though, in that situation you'd want to 
specify a "path="/"" attribute, like in your example)

If that's *not* working for you, you may want to look closer at whether Tomcat 
is reporting errors in its log files.  The errors in the Tomcat logs may 
provide us with more information about what Tomcat doesn't like about your 
configuration.  So, please send any errors to this list and hopefully we can 
help you figure them out.

Tim

On Wed, Oct 31, 2018 at 10:13 AM Cameron, Jacob 
mailto:jacob.came...@uleth.ca>> wrote:
Hi Everyone,

Windows Server 2016, Tomcat 8.5, DSpace 6.3.

I’ve setup the context path in server.xml to be path=“/” docBase=”[dspace 
path]\webapps\xmlui” and I get a blank page when I go to 
http://localhost:8080/, however if I go to http://localhost:8080/xmlui it works 
fine.

I’ve tried the context fragments, with ROOT.xml in 
tomcat\conf\catalina\localhost\ and still have the same issue.  Restarted the 
tomcat server, restarted the server, still having not luck.  Any suggestions?




Jake
--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
--
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-tech] View Statistics links not working

[Sean Kalynuk]

 [NC]
RewriteCond %{REQUEST_URI} "^/statistics-home"[NC]
RewriteCond %{REQUEST_URI} "^/search-statistics"  [NC]
RewriteCond %{REQUEST_URI} "^/workflow-statistics"   [NC]
RewriteRule (.*) 
http://%{HTTP_HOST}:8080%{REQUEST_URI}<http://%25%7bHTTP_HOST%7d:8080%25%7bREQUEST_URI%7d>
 [R,L]

DocumentRoot /dspace/webapps/xmlui
ServerName dspace36a.library.uaf.edu<http://dspace36a.library.uaf.edu>
ServerAlias scholarworks

ErrorLog logs/dspace36a.library.uaf.edu-https-error_log
CustomLog logs/dspace36a.library.uaf.edu-https-access_log combinedssl
RewriteLog logs/dspace36a-rewrite

Include conf.d/ssl.include
Include conf.d/ssl.include.star
### ^ these point to a file which specifies where the ssl certificates
###   live on the host.

#   ProxyPass / http://127.0.0.1:8080/  retry=10 connectiontimeout=5
ProxyPass /  http://127.0.0.1:443/retry=10 connectiontimeout=5
### ^ this tells httpd to redirect it's / to localhost port 8080

#timeout=300

#   ProxyPassReverse /  http://127.0.0.1:8080/  retry=10
ProxyPassReverse /   http://127.0.0.1:443/retry=10
### ^ this tells httpd that tomcat's url's should be rewritten to look
###   like they're coming from httpd.

ProxyPreserveHost On
### ^ this tells httpd to keep the Host: information from the client and
### pass it on to tomcat.

#SSLUseStapling on
### Added due to error when starting apache.  Dayne Ellanna




#
### Redirect insecure ports to secure port 443
ServerAdmin uaf-libra...@alaska.edu<mailto:uaf-libra...@alaska.edu>
RewriteEngine On
RewriteCond %{HTTPS} on
RewriteRule (.*) 
http://%{HTTP_HOST}:8080/%{REQUEST_URI}<http://%25%7bHTTP_HOST%7d:8080/%25%7bREQUEST_URI%7d>
 [R,L]
DocumentRoot /dspace/webapps/xmlui
ServerName dspace36a.library.uaf.edu<http://dspace36a.library.uaf.edu>
ServerAlias scholarworks

ErrorLog logs/dspace36a.library.uaf.edu-error_log
CustomLog logs/dspace36a.library.uaf.edu-access_log common
RewriteLog logs/dspace36a-rewrite

ProxyPass / http://127.0.0.1:8080/  retry=10 connectiontimeout=5
### ^ this tells httpd to redirect it's / to localhost port 443

#timeout=300
ProxyPassReverse / http://127.0.0.1:8080/  retry=10
### ^ this tells httpd that tomcat's url's should be rewritten to look
###   like they're coming from httpd.

#   ProxyPreserveHost On
### ^ this tells httpd to keep the Host: information from the client and
### pass it on to tomcat.



[tomcat]/conf/server.xml

 

So I managed to break both ports 80 and 443 but, amazingly port 8080 works like 
a charm
and gives the statistics I've been trying to see for many weeks! I suspect the 
new problem
is in the vhosts.conf file but haven't yet caught what's going wrong.
http://dspace36a.library.uaf.edu:8080/

The stats links now work for the whole site (Home Page) and for individual 
items, although
I'm not entirely sure the single item stats are working completely correctly 
since I haven't
seen them working until now and there are often blanks within the returned 
information.

=



On Friday, October 19, 2018 at 1:10:05 PM UTC-8, 
wlruth...@alaska.edu<mailto:wlruth...@alaska.edu> wrote:

I set "solr.server" to use port 8080 in /dspace/config/dspace.cfg as well as 
"server" in solr-statistics.cfg and "solr.url" in oai.cfg.
Looks like progress, it still fails but the error messages changed:
2018-10-19 12:58:58,999 ERROR 
org.dspace.app.xmlui.aspect.statistics.StatisticsTransformer @ Error occurred 
while creating statistics for home page
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Expected 
mime type application/octet-stream but got text/html. Apache Tomcat/9.0.0.M17 - Error reporth1 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
 h2 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
 h3 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
 body {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} 
b {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} p 
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}
 a {color:black;} a.name<<a  rel="nofollow" href="http://a.name">http://a.name</a>> {color:black;} .line 
{height:1px;background-color:#525D76;border:none;} 
HTTP Status 404 - /solr/se

RE: [dspace-tech] View Statistics links not working

[Sean Kalynuk]

Hi Walter,

Since there is redirect logic involved, how about updating your solr.server 
parameter to point directly to the Tomcat solr webapp on port 8080?

solr.server = http://localhost:8080/solr

Not entirely sure, but I’m guessing this type of change requires a Tomcat 
restart.

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
wlrutherf...@alaska.edu
Sent: October 19, 2018 2:26 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] View Statistics links not working


Hey Sean,

I started to say I saw nothing in the logs but I just saw a redirection error 
in dspace.log.2018-10-19 that I haven't seen before:
2018-10-19 10:51:13,345 ERROR 
org.dspace.app.xmlui.aspect.statistics.StatisticsTransformer @ Error occurred 
while creating statistics for home page
org.apache.solr.client.solrj.SolrServerException: Server at 
http://localhost/statistics sent back a redirect (302).
...
Rather than include the entire ~180 line stack trace, here is the 
/etc/httpd/conf.d/vhosts.conf file which handles HTTP redirection although I 
think
we may have been having problems with the statistics links even before adding 
this file:
[root@dspace36a conf.d]# cat vhosts.conf

#
### Redirect insecure ports to secure port 443
ServerAdmin 
uaf-library-it-d...@alaska.edu<mailto:uaf-library-it-d...@alaska.edu>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) 
https://%{HTTP_HOST}:443%{REQUEST_URI}<https://%25%7bHTTP_HOST%7d:443%25%7bREQUEST_URI%7d>
 [R,L]
DocumentRoot /dspace/webapps/xmlui
ServerName dspace36a.library.uaf.edu<http://dspace36a.library.uaf.edu/>
ServerAlias scholarworks

ErrorLog logs/dspace36a.library.uaf.edu-error_log
CustomLog logs/dspace36a.library.uaf.edu-access_log common
RewriteLog logs/dspace36a-rewrite

ProxyPass / http://127.0.0.1:443/  retry=10 connectiontimeout=5
### ^ this tells httpd to redirect it's / to localhost port 443

#timeout=300
ProxyPassReverse / http://127.0.0.1:443/  retry=10
### ^ this tells httpd that tomcat's url's should be rewritten to look
###   like they're coming from httpd.

#   ProxyPreserveHost On
### ^ this tells httpd to keep the Host: information from the client and
### pass it on to tomcat.



#http://dspace36a.library.uaf.edu:443/>>

### ^ this creates a httpd server that listens on port 443.

ServerAdmin 
uaf-library-it-d...@alaska.edu<mailto:uaf-library-it-d...@alaska.edu>
DocumentRoot /dspace/webapps/xmlui
ServerName dspace36a.library.uaf.edu<http://dspace36a.library.uaf.edu/>
ServerAlias scholarworks

ErrorLog logs/dspace36a.library.uaf.edu-https-error_log
CustomLog logs/dspace36a.library.uaf.edu-https-access_log combinedssl
RewriteLog logs/dspace36a-rewrite

Include conf.d/ssl.include
Include conf.d/ssl.include.star
### ^ these point to a file which specifies where the ssl certificates
###   live on the host.

ProxyPass / http://127.0.0.1:8080/  retry=10 connectiontimeout=5
#   ProxyPass / http://127.0.0.1:443/  retry=10 connectiontimeout=5
### ^ this tells httpd to redirect it's / to localhost port 8080

#timeout=300

ProxyPassReverse /  http://127.0.0.1:8080/  retry=10
#   ProxyPassReverse /  http://127.0.0.1:443/  retry=10
### ^ this tells httpd that tomcat's url's should be rewritten to look
###   like they're coming from httpd.

ProxyPreserveHost On
### ^ this tells httpd to keep the Host: information from the client and
### pass it on to tomcat.



Ports 80, 443, 8000, and 8080 are active for TCP. Port 8000 is used by the 
handle-server but 8080 should also be unsecured.



On Friday, October 19, 2018 at 8:46:33 AM UTC-8, Sean Kalynuk wrote:
Hi Walter,

Do you see errors in the logs when visiting the following page?

https://dspace36a.library.uaf.edu/search-statistics

At least on that page I got “There was an error while generating the search 
statistics, please try again later.”

You can also see an error message when visiting

https://dspace36a.library.uaf.edu/workflow-statistics

--
Sean

From: dspac...@googlegroups.com 
> On Behalf Of 
wlruth...@alaska.edu
Sent: October 18, 2018 2:52 PM
To: DSpace Technical Support >
Subject: Re: [dspace-tech] View Statistics links not working

This is maddening and taking far longer than it should, mostly because I can't 
tell where the problem is located.
I've setup all of the configuration variables mentioned in the manual but I'm 
not seeing anything in the logfiles
that says what's wrong. It could be a combination of Tomcat/DSpace, httpd, 
solr, ... The only other similar posts
I've seen here haven't had solutions. It doesn't help

RE: [dspace-tech] View Statistics links not working

[Sean Kalynuk]

Hi Walter,

Do you see errors in the logs when visiting the following page?

https://dspace36a.library.uaf.edu/search-statistics

At least on that page I got “There was an error while generating the search 
statistics, please try again later.”

You can also see an error message when visiting

https://dspace36a.library.uaf.edu/workflow-statistics

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
wlrutherf...@alaska.edu
Sent: October 18, 2018 2:52 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] View Statistics links not working

This is maddening and taking far longer than it should, mostly because I can't 
tell where the problem is located.
I've setup all of the configuration variables mentioned in the manual but I'm 
not seeing anything in the logfiles
that says what's wrong. It could be a combination of Tomcat/DSpace, httpd, 
solr, ... The only other similar posts
I've seen here haven't had solutions. It doesn't help that I haven't see the 
statistics links working so I'm not quite
sure even what to expect.

For example: I can see https://dspace36a.library.uaf.edu/solr but that looks 
more like an administrator page. But
I don't need to be logged in at all to see it and I'm pretty sure that's not 
the statistics page. If I try this instead:
https://dspace36a.library.uaf.edu/statistics I get an entirely blank page. In 
my experience that means it's being
handled (it's not returning an error) but the output is null.

I can attach config files or logs but which would be most useful to help 
troubleshoot this problem?

 Thank you.

   Walter R.


On Wednesday, October 10, 2018 at 12:17:03 PM UTC-8, 
wlruth...@alaska.edu wrote:
I am occasionally seeing errors like this in the catalina.out file:
Error using query type: 2
[WARN] deprecation - The 'component-configurations' section in the sitemap is 
deprecated. Please check for alternatives.
Error using query *:*
Error using query statistics_type:workflow AND NOT(previousWorkflowStep: SUBMIT)
Error using query type: 2 AND  id:2695
Error using query type: 0 AND owningItem:2695
Error using query type: 2 AND  id:3677
Error using query type: 0 AND owningItem:3677
The four digit numbers appear to be valid item numbers so I'm not sure what's 
generating the errors. So I'm slogging
through the manual and sitemaps to see if I can trace what happens when the 
"View Usage Statistics" link is clicked.



On Tuesday, October 9, 2018 at 2:48:54 PM UTC-8, 
wlruth...@alaska.edu wrote:
Rats... couldn't be that easy.

Finding very few non-INFO messages in the logs. I did find an entry in 
catalina.out that at least tells me it is/was running solr (perhaps with memory 
leaks).
01-Jun-2017 01:23:38.504 WARNING [localhost-startStop-2] 
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web 
application [solr] appears to have started a thread named 
[MultiThreadedHttpConnectionManager cleanu
p] but has failed to stop it. This is very likely to create a memory leak. 
Stack trace of thread:

The rest of that log is either warnings about deprecated features or lines like 
these (which doesn't look fatal):
01-Jun-2017 05:57:35.306 WARNING [localhost-startStop-1] 
org.apache.solr.handler.component.SpellCheckComponent.inform No queryConverter 
defined, using default converter

I made the mistake of turning on DEBUG logging. But after filtering out 
thousands of DEBUG messages I see:
2018-10-09 13:04:25,728 INFO  org.dspace.usage.LoggerUsageEventListener @ 
anonymous:session_id=7D74E0A56FFA3493875B4B5436B875C6:ip_addr=127.0.0.1:view_item:handle=11122/6045
2018-10-09 13:04:25,738 ERROR org.dspace.statistics.SolrLogger @ 
org.apache.commons.httpclient.ProtocolException: The server 
scholarworks.alaska.edu failed to respond with 
a valid HTTP response
org.apache.solr.client.solrj.SolrServerException: 
org.apache.commons.httpclient.ProtocolException: The server 
scholarworks.alaska.edu failed to respond with 
a valid HTTP response

Perhaps Solr is trying to use HTTP while the server is configured for (mostly) 
HTTPS with a few exceptions. There was something a co-worker had added to the 
web.xml file
to force HTTPS but I don't see it now. He might've removed it and put all that 
in the httpd configuration. If he didn't that might be the problem - the two of 
them fighting.


On Tuesday, October 9, 2018 at 11:51:14 AM UTC-8, Tim Donohue wrote:
Hi Walter,

I don't think those "messages.xml" notices have anything to do with this Solr 
Statistics problem.  That "messages.xml" file is not directly related to Solr.  
The XMLUI also looks for those files in several different locations, so if it 
doesn't find them in one place, it will look elsewhere.  So, those log lines 
can likely be ignored.

What you should be looking more closely at is whether any errors/warnings are 
occurring in the dspace.log files (or Tomcat logs) when you:
(

RE: [dspace-tech] OAI-PMH issue

[Sean Kalynuk]

Hi Peter,

According to the Tomcat documentation, the path attribute can only be used in a 
Context element if it is defined in server.xml. (See 
https://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Common_Attributes 
for Tomcat 8.5).

Also, see https://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Naming 
for information on naming the .xml file to change the context path. If you are 
using an older version of Tomcat, I believe the rules are the same.

In your case, I think you will need to name it:

repository#oai.xml

That will define the context path as /repository/oai

Also, the path to the .xml file is important. It should be defined in 
$CATALINA_BASE/conf/Catalina/sample.com/repository#oai.xml (for example) so 
that requests to sample.com find the correct webapp. And, the server.xml file 
should have a Host element defined for sample.com.

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
admin
Sent: October 5, 2018 12:26 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] OAI-PMH issue

Hi Tim,

for now I just added "path" into oai.xml file:

restarted Tomcat, but it didn't change anything. DSpace still shows "page not 
found" when I click on the OAI-PMH URL (Harvesting tab of the Control Panel), 
which is https://sample.com/repository/oai

I didn't change "oai.url" for now; it is "${dspace.baseUrl}/oai" and my 
"${dspace.baseUrl}" is https://sample.com/repository, so if I understand it 
correctly it is ok?

Peter


W dniu środa, 3 października 2018 22:33:50 UTC+1 użytkownik Tim Donohue napisał:
Hi Peter,

To me, it sounds like you'll need to tell Tomcat that "/repository/oai" should 
reference the OAI webapp. From the behavior you are noting, it sounds like 
Tomcat only knows that "/repository" is the DSpace UI webapp (either XMLUI or 
JSPUI).  So, it's attempting to send "/repository/oai" on to that DSpace UI 
webapp.

It may be as simply as having something like this in your Tomcat configuration:



In addition, you also may need to modify the "oai.url" configuration in your 
local.cfg (or in oai.cfg directly):
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/modules/oai.cfg#L12

Beyond that, I don't think you should need to modify the OAI web application 
itself.  It should be deployable to any path.

Let us know on this list if this helps you figure it out

- Tim

On Wed, Oct 3, 2018 at 4:25 PM admin > wrote:
I added that to the url, but nothing changes. Still url not found note 
displayed by DSpace.


W dniu środa, 3 października 2018 15:03:58 UTC+1 użytkownik Sean Kalynuk 
napisał:
Hi,

Try adding this after oai:

/request?verb=Identify

--
Sean

From: dspac...@googlegroups.com<mailto:dspac...@googlegroups.com> 
mailto:dspac...@googlegroups.com>> On Behalf Of admin

Sent: October 2, 2018 2:16 PM
To: DSpace Technical Support 
mailto:dspac...@googlegroups.com>>
Subject: [dspace-tech] OAI-PMH issue

Hi,

My DSpace 6.3 has been installed in a subdirectory: 
https://sampledomain.com/repository
I noticed that OAI-PMH URL, which is https://sampledomain.com/repository/oai, 
doesn't seem to work – clicking on it takes me to the DSpace's “Page not found. 
We can't find the page you asked for.”

I was wondering if I need to configure OAI somehow additionally because I have 
DSpace in a subdirectory (and behind ssl)?
I noticed for example that [dspace]/config/crosswalks/oai/description.xml 
hasn't got subdirectory included (do I need it there at all?):
sampledomain.com<http://sampledomain.com>
oai:sampledomain.com:123456789/1234<http://sampledomain.com:123456789/1234>

Or can it be simply that OAI is not available from Tomcat...?


Best, Peter
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech...@googlegroups.com<mailto:dspace-tech...@googlegroups.com>.
To post to this group, send email to 
dspac...@googlegroups.com<mailto:dspac...@googlegroups.com>.

Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech...@googlegroups.com.
To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For m

RE: [dspace-tech] OAI-PMH issue

[Sean Kalynuk]

Hi,

Try adding this after oai:

/request?verb=Identify

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
admin
Sent: October 2, 2018 2:16 PM
To: DSpace Technical Support 
Subject: [dspace-tech] OAI-PMH issue

Hi,

My DSpace 6.3 has been installed in a subdirectory: 
https://sampledomain.com/repository
I noticed that OAI-PMH URL, which is https://sampledomain.com/repository/oai, 
doesn't seem to work – clicking on it takes me to the DSpace's “Page not found. 
We can't find the page you asked for.”

I was wondering if I need to configure OAI somehow additionally because I have 
DSpace in a subdirectory (and behind ssl)?
I noticed for example that [dspace]/config/crosswalks/oai/description.xml 
hasn't got subdirectory included (do I need it there at all?):
sampledomain.com
oai:sampledomain.com:123456789/1234

Or can it be simply that OAI is not available from Tomcat...?


Best, Peter
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-tech] Re: Problems with Orcid in dspace 6.3

[Sean Kalynuk]

Just following up that my tests also confirmed that PR-2195 fixes a bunch of 
issues and I added a comment to https://jira.duraspace.org/browse/DS-3999 with 
some details.
--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
Darryl Friesen
Sent: September 20, 2018 4:36 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] Re: Problems with Orcid in dspace 6.3


Great.  I've left a comment in DS-3999 stating that it appears to correct the 
issue.

- Darryl



On Thursday, September 20, 2018 at 3:26:06 PM UTC-6, Tim Donohue wrote:
Hi Darryl,

We welcome *either* code reviewers or testers.  So, simply adding your feedback 
that the PR "worked for you" and resolved  issues is good feedback.  If you 
don't have a GitHub account, you can also just add your testing feedback to the 
original JIRA ticket (https://jira.duraspace.org/browse/DS-3999).

Definitely don't worry if you cannot provide a code review.  We have plenty of 
volunteers that can provide quick code reviews.  Often we are most lacking in 
good *testers* (especially folks who've seen the issue & know how to trigger 
it, and can therefore easily tell if the code "fixes it").

Thanks for your testing!

Tim




On Thu, Sep 20, 2018 at 4:21 PM Darryl Friesen 
> wrote:

I implemented the change to Orcidv2AuthorityValue.java as per PR 2195 and 
rolled that out to our test server.  This seems to have fixed most (all?) of 
the issues mentioned in this thread, specifically:


  *   adding an additional author no longer seems to remove orcid_id from the 
Solr database
  *   Running index-authority also no longer removes orcid_id from Solr
  *   orcid is now displayed when using the author Lookup feature.  This is an 
important issue for us (and Sean as well i assume since he also mentioned it) 
we prefer ORCID whenever possible.  This will help eliminate dups in authority 
control now that people can see the ORCID ID again
I did not try UpdateAuthorities to see if the issues mentioned by Sean were 
still an issue.

Tim, I'm not a Java programmer -- I can help out if you want to migrate DSpace 
to one of the PHP frameworks though :)  -- so I don't feel comfortable making 
an approving review of the code in the PR;  I'm not sure if the code in that PR 
is "good" or not, nor how it might affect the rest of the DSpace codebase, but 
I could leave a comment in the PR if that helps.  It seems to have fixed a lot 
of issues for me.

- Darryl





On Thursday, September 20, 2018 at 12:42:54 PM UTC-6, Tim Donohue wrote:
All,

For anyone affected by the index-authority bug described in 
https://jira.duraspace.org/browse/DS-3999, we could use more testers for the 
proposed fix at: https://github.com/DSpace/DSpace/pull/2195 .  The quicker bug 
fixes get tested or reviewed, the quicker we are able to move them along into 
the actual codebase.  While we do have some volunteers that help us with 
testing/reviewing, finding additional community users can always speed up the 
process.

- Tim

On Thu, Sep 20, 2018 at 1:12 PM Sean Kalynuk 
mailto:sean.k...@umanitoba.ca>> wrote:
Hi Darryl,

I’m currently experimenting with DSpace 6.3 and have the same or similar issues.


• index-authority is removing orcid_id but leaving the authority_type 
as “orcid” (see https://jira.duraspace.org/browse/DS-3999)

• The orcid_id is not displaying in the Author Lookup for authors added 
from ORCID, so, when there are duplicate author entries, you cannot 
differentiate authority_type=”orcid_id” from authority_type=”person” for the 
same person

• UpdateAuthorities has multiple issues (-i option results in NPE and a 
full update only runs on 10 records) (see 
https://jira.duraspace.org/browse/DS-3302)

--
Sean

From: dspac...@googlegroups.com<mailto:dspac...@googlegroups.com> 
mailto:dspac...@googlegroups.com>> On Behalf Of 
Darryl Friesen

Sent: September 20, 2018 11:18 AM
To: DSpace Technical Support 
mailto:dspac...@googlegroups.com>>

Subject: [dspace-tech] Re: Problems with Orcid in dspace 6.3

While I haven't experimented with what happens when adding additional authors, 
I've noticed that the "orcid_id" field also seems to get removed by the 
"index-authority" job that runs as part of cron.  Perhaps there's a common task 
that is executed during both processes that is messing up the Solr database.

I've also noticed issues with the authority control/ORCID Lookup features 
during submission (and when editing).  The OCRID seems to be lost there too, 
and the authority control will happily create duplicates. I posted about it a 
couple weeks ago:

 https://groups.google.com/d/msg/dspace-tech/4nJRVyn8Hk8/M0TnMAIBCgAJ

I'm happy the ORCID lookup works again, but there seems to be some issues with 
it.

- Darryl


On Sunday, September 16, 2018 at 3:37:20 AM UTC-6, Stefanie Behnke wrote:
Dear all,
we use Ds

RE: [dspace-tech] Re: Problems with Orcid in dspace 6.3

[Sean Kalynuk]

Hi Darryl,

I’m currently experimenting with DSpace 6.3 and have the same or similar issues.


· index-authority is removing orcid_id but leaving the authority_type 
as “orcid” (see https://jira.duraspace.org/browse/DS-3999)

· The orcid_id is not displaying in the Author Lookup for authors added 
from ORCID, so, when there are duplicate author entries, you cannot 
differentiate authority_type=”orcid_id” from authority_type=”person” for the 
same person

· UpdateAuthorities has multiple issues (-i option results in NPE and a 
full update only runs on 10 records) (see 
https://jira.duraspace.org/browse/DS-3302)

--
Sean

From: dspace-tech@googlegroups.com  On Behalf Of 
Darryl Friesen
Sent: September 20, 2018 11:18 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: Problems with Orcid in dspace 6.3

While I haven't experimented with what happens when adding additional authors, 
I've noticed that the "orcid_id" field also seems to get removed by the 
"index-authority" job that runs as part of cron.  Perhaps there's a common task 
that is executed during both processes that is messing up the Solr database.

I've also noticed issues with the authority control/ORCID Lookup features 
during submission (and when editing).  The OCRID seems to be lost there too, 
and the authority control will happily create duplicates. I posted about it a 
couple weeks ago:

 https://groups.google.com/d/msg/dspace-tech/4nJRVyn8Hk8/M0TnMAIBCgAJ

I'm happy the ORCID lookup works again, but there seems to be some issues with 
it.

- Darryl


On Sunday, September 16, 2018 at 3:37:20 AM UTC-6, Stefanie Behnke wrote:
Dear all,
we use Dspace 6.3, XMLUI Interface and ORCID enabled.
Submitting a new item with 2 authors works. The result in the authority shows: 
(example for one author)
  {
"id": "75e2dd03-7cdf-4e21-9b1d-293f02d3c0cf",
"field": "dc_contributor_author",
"value": "Behnke, Stefanie",
"deleted": false,
"creation_date": "2018-09-16T09:01:40.474Z",
"last_modified_date": "2018-09-16T09:01:40.474Z",
"authority_type": "orcid",
"first_name": "Stefanie",
"last_name": "Behnke",
"orcid_id": "-0001-5923-423X"
  },

Trying to add a third author with ORCID to this item make the “orcid_id” for 
the existing authors vanish from the authority:
  {
"id": "75e2dd03-7cdf-4e21-9b1d-293f02d3c0cf",
"field": "dc_contributor_author",
"value": "Behnke, Stefanie",
"deleted": false,
"creation_date": "2018-09-16T09:01:40.474Z",
"last_modified_date": "2018-09-16T09:01:40.474Z",
"authority_type": "orcid",
"first_name": "Stefanie",
"last_name": "Behnke"
  },

I cannot imagine that this should be the intended behaviour, so I think this is 
a bug.
Any help is much appreciated.
Best regards
Stefanie
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: DSpace 6.3 OAI indexing is failing

[Sean . Kalynuk]

Hi Christian,

I also encountered this while testing 6.3 the other day.

In my case, I modified both the willChangeStatus() and 
getMostRecentModificationDate() methods in XOAI.java to check for a null 
ResourcePolicy Group (similar to what you suggested).

After the change I was able to do a full import (dspace oai import -c).

However, since I'm new to DSpace, I'm also not clear on whether all 
ResourcePolicy objects with READ action should have Groups assigned.

--
Sean

On Tuesday, 24 July 2018 07:44:32 UTC-5, Christian Scheible wrote:
>
> Hi all, 
>
> we have recently upgraded to DSpace 6.3 and are experiencing problems 
> with the update of the OAI Solr index. 
> We have a NullPointerException at 
>
> https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-oai/src/main/java/org/dspace/xoai/app/XOAI.java#L438
>  
> which was introduced with DSpace 6.3. 
>
> The added code that leads to the problem was added in order to respect 
> embargoed items at the OAI interface. 
>
> I could easily solve this by changing the line to: if (policy.getGroup() 
> != null && policy.getGroup().getName() != null && 
> policy.getGroup().getName().equals("Anonymous")) { 
>
> But I am wondering if there is something messed up with our 
> ResourcePolicies. 
> So my question is: 
>
> Should ResourcePolicies for Items of type Read always contain a 
> EPersonGroup? 
>
> Kind Regards 
> Christian 
>
> -- 
> Christian Scheible 
> Softwareentwickler / Abt. Content-basierte Dienste 
> Kommunikations-, Informations-, Medienzentrum (KIM) 
> Universität Konstanz 
> 78457 Konstanz 
> +49 (0)7531 / 88-2857 
> Raum B 703 
>
>
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.