[dspace-tech] customizing the untyped-item component

[bens...@gmail.com]

dspace 7.6.2

using the custom theme.

 If I modify untyped-item.component.ts in 
dspace-angular-dspace-7.6.2/src/themes/custom/app/item-page/simple/item-types/untyped-item
 
styleUrls: ['./untyped-item.component.scss'],
  //styleUrls: 
['../../../../../../../app/item-page/simple/item-types/untyped-item/untyped-item.component.scss'],
   templateUrl: './untyped-item.component.html',
  //templateUrl: 
'../../../../../../../app/item-page/simple/item-types/untyped-item/untyped-item.component.html',
  
  It does not use the local copy of untyped-item.component.html. It is 
still using the one in 
  
dspace-angular-dspace-7.6.2/src/app/item-page/simple/item-types/untyped-item/
  
  
but if I modify footer.component.ts in 
 dspace-angular-dspace-7.6.2/src/themes/custom/app/footer

   styleUrls: ['./footer.component.scss'],
  //styleUrls: ['../../../../app/footer/footer.component.scss'],
  templateUrl: './footer.component.html'
  //templateUrl: '../../../../app/footer/footer.component.html'
  
 It works using the local copy of the footer.component.html

What am I missing to get it to work?

-- 
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/545e25fd-7b8b-4352-89b4-9d1de8ba70a3n%40googlegroups.com.

Re: [dspace-tech] Indexing Issues with University Institutional Repository

[Sean Carte]

Thanks, Dr Schrader. Unfortunately, that isn't the case with my repository,
which does provide the citation_pdf_url meta tag in the item pages, yet is
not indexed by Google Scholar.

Sean

On Mon, 7 Oct 2024 at 19:14, Jarmo Schrader <
jarmo.schra...@uni-hildesheim.de> wrote:

> Hi,
>
> we had the same problem and I think I found the solution today:
>
> Google Scholar needs certain metadata-tags in the  section of the
> site in order to index your repository properly. One of them is
> citation_pdf_url. This should be the url of the (PDF)fulltext document. On
> your server the tag looks like this:  "http://localhost:4000/bitstreams/59de15c5-8de0-4fb4-b90f-66979d4a1ee7/download";
> >
>
>
> Instead of the hostname there ist a "localhost" in the url. This is
> probably because you are using a proxy in front of dspace.
>
> For us the solution was to add a line with "ProxyPreserveHost On" to our
> Apache-Configuration. Now citation_pdf_url lists the correct URL for the
> pdf. This is our apache config:
>
>   ProxyPreserveHost On
>   ProxyPass /server http://127.0.0.1:8080/server
>   ProxyPassReverse /server http://127.0.0.1:8080/server
>   ProxyPass / http://127.0.0.1:4000/
>   ProxyPassReverse / http://127.0.0.1:4000/
>   RequestHeader set X-Forwarded-Proto https
>   RequestHeader set X-Forwarded-Host our.repository-domain.com
>
>
> (I am not an Apache expert, there might be a better solution, but it seems
> to work. Since I only found this today, I am not 100% sure it will fix the
> problem with googl scholar but it definitely is something that needs to be
> fixed)
>
> I found the solution by watching this helpful video from a Person working
> for Google Scholar with tips for repositories:
> https://www.youtube.com/watch?v=C-miRaROsaE
> Here is the presentation from the video:
> https://www.carl-abrc.ca/wp-content/uploads/2021/01/Google_Scholar_webinar_Jan2021.pdf
>
> Good luck with your repository!
>
> Best regards
> Jarmo
>
> Am 25.09.2024 um 11:01 schrieb Fares Mezrag:
>
> Dear Dspace Technical Team,
>
> I have an issue with the indexing of our institutional repository,
> University of M'sila Institutional Repository (
> https://dspace.univ-msila.dz/), on Google Scholar.
>
> In September 2023, our repository boasted approximately 28,900 indexed
> items. However, in December 2023, we witnessed a dramatic decrease. All
> previously indexed items have vanished, leaving our current count at zero
> on Google Scholar (March 2024). With the knowledge that we were using the
> old version of DSpace (Version 4.2), we have updated DSpace to version
> 7.6.1 since April 2024. Additionally, we followed the official search
> engine optimization guide. Unfortunately, the problem persists.
>
> For your reference, here's a search for our repository on Google Scholar:
>
>
> https://scholar.google.com/scholar?hl=en&as_sdt=0%2C5&q=site%3Adspace.univ-msila.dz&oq=
>
> Our university's technical team has tirelessly attempted to resolve the
> issue, but to no avail.
>
> We urgently request any guidance or information you can offer to rectify
> the indexing problems plaguing our repository. Additionally, if possible,
> we'd appreciate knowing the point of contact at Google Scholar who handles
> such matters.
> Sincerely,
> Dr Fares Mezrag
> IT Manager
> M’sila University --
> 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/9c7f409a-361f-4977-aa29-86b342a4272bn%40googlegroups.com
> 
> .
>
>
> --
> Dr. Jarmo Schrader
> stellv. Bibliotheksleiter
> Fachreferat und EDV
> Universität Hildesheim
> Universitätsbibliothek
> Universitätsplatz 1
> 31141 Hildesheim
>
> Tel: +49 (0) 5121 - 883 - 93004
> jarmo.schra...@uni-hildesheim.de
>
> --
> 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/cea56050-0c9a-4b33-a826-13b98a6d4598%40uni-hildesheim.de
> 
> .
>

-- 
All mess

RE: [dspace-tech] Error loading DataCite schema v.4 crosswalk stylesheet

[Kiriaki Roditi]

Thank you for the prompt response!
The only part of the file I have edited, compared to the one referenced from 
Github, is in the beginning, the properties for
  and 

I have tested with some alternative versions of DIM2DataCite.xsl published in 
an August commit and the error is always in the same line of the resourceType 
element.
https://github.com/DSpace/DSpace/blob/e8a2e73fcc9b7944408daf6a6f683b69939949cd/dspace/config/crosswalks/DIM2DataCite.xsl#L242
 
Our institution 's metadata is in Greek (language code: el), dc.type field is 
required and filled for all repository items and it works effortlessly for 
Datacite Schema v.3

Is there some other configuration file (i.e. pom.xml, spring...) that I should 
declare the new Datacite Schema version?

Many thanks,
Kiriaki

-Original Message-
From: mw...@mhw.library.indianapolis.iu.edu 
 On Behalf Of mw...@iu.edu
Sent: Monday, October 7, 2024 5:22 PM
To: dspace-tech@googlegroups.com
Subject: Re: [dspace-tech] Error loading DataCite schema v.4 crosswalk 
stylesheet

On Mon, Oct 07, 2024 at 12:16:32PM +, Kiriaki Roditi wrote:
> You don't often get email from kiriaki.rod...@elidoc.gr. Learn why this is 
> important
> Hello to All,
> 
> Having trouble updating the Datacite crosswalk to use Schema version 4 on a 
> DSpace v.6.3 installation.
> I have updated 
> DIM2DataCite.xsl
>  , dspace.fg, local.cfg and DataCiteConnector.java to use 
> http://datacite.org/schema/kernel-4
> 
> The error in the console when I try to update a DOI is
> ERROR:  'Syntax error in ''.'
> FATAL ERROR:  'line 242: Required attribute 'select' is missing.'

It appears that your edited DIM2DataCite.xsl has an error on line 242.
Probably an 'apply-templates' element is missing its required 'select'.

> This is the excerpt from the logs
> ERROR org.dspace.content.crosswalk.XSLTCrosswalk @ Failed to initialize 
> XSLTCrosswalk(DataCite):  
> javax.xml.transform.TransformerConfigurationException: line 242: Required 
> attribute 'select' is missing.
> ERROR org.dspace.identifier.doi.DataCiteConnector @ Caught an 
> CrosswalkException while reserving a DOI for DSO with type 2 and ID 
> 6ba15ba8-0fae-43e7-b7cc-73de23d9098d. Won't reserve the doi.
> org.dspace.content.crosswalk.CrosswalkInternalException: Failed to initialize 
> transformer, probably error loading stylesheet.
> at 
> org.dspace.content.crosswalk.XSLTDisseminationCrosswalk.disseminateElement(XSLTDisseminationCrosswalk.java:225)
> at 
> org.dspace.identifier.doi.DataCiteConnector.reserveDOI(DataCiteConnector.java:422)
> at 
> org.dspace.identifier.doi.DataCiteConnector.updateMetadata(DataCiteConnector.java:582)
> at 
> org.dspace.identifier.DOIIdentifierProvider.updateMetadataOnline(DOIIdentifierProvider.java:420)
> at 
> org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:594)
> at 
> org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:240)
> at 
> org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:71)
> 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)
> ERROR org.dspace.identifier.doi.DOIOrganiser @ It wasn't possible to update 
> this identifier:  doi: Exceptions code:  CONVERSION_ERROR
> org.dspace.identifier.doi.DOIIdentifierException: CrosswalkException occured 
> while converting ITEM/6ba15ba8-0fae-43e7-b7cc-73de23d9098d using crosswalk 
> DataCite.
> at 
> org.dspace.identifier.doi.DataCiteConnector.reserveDOI(DataCiteConnector.java:440)
> at 
> org.dspace.identifier.doi.DataCiteConnector.updateMetadata(DataCiteConnector.java:582)
> at 
> org.dspace.identifier.DOIIdentifierProvider.updateMetadataOnline(DOIIdentifierProvider.java:420)
> at 
> org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:594)
> at 
> org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:240)
> at 
> org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>

[dspace-tech] Private message regarding: DSpace 7.5 - How can I use my own domain? Please help.

[Marshal Phiri]

I have made changes to make DSpace 8 available on LAN, however when I 
assign an IP address, the the PC is viewable on LAN but produces 500 Error. 
PLease send me the detailed configurations you have made for the PC to 
accessible on LAN. Your assistance is greatly appreciated.

On Wednesday, July 10, 2024 at 11:56:47 PM UTC+2 DSpace Technical Support 
wrote:

Hi,

If you are still having issues getting DSpace 7 running on your own domain, 
then I'd recommend following the instructions in the Installation Guide 
about setting up Apache or Nginx as a proxy in front of *both* the User 
Interface (frontend) and REST API (backend).  Then you can configure your 
domain easily in Apache or Nginx and run it via HTTPS.

See the Installation guide at 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace   For the 
details about using Apache or Nginx, see step 17 of the Backend Install and 
step 8 of the Frontend Install.

Tim

On Friday, June 28, 2024 at 2:48:06 PM UTC-5 lala...@gestion.uta.cl wrote:

Hello colleagues, I have installed dspace 7.5, I have done everything, I 
installed it on a server and on IP:4000 it works perfectly, you can access 
the entire university using the same network, but now I need to be able to 
access from the university domain.

http://[ip]:4000/home works perfectly
http://[domain name]:4000/home gives me the error 500 service unavailable.

I have seen some posts with similar things, but I would appreciate it not 
working, could you tell me how to do it? directions, something, I am 
desperately looking for information and I can't find it, it is also 
important to mention that I do not want to lose all the interface 
modifications I have made as well as all the educational resources 
deposited on the platform and their statistics.

I will be attentive to your comments, thank you very much colleagues.

-- 
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/d5392cad-567d-4d68-927f-faee6288dabcn%40googlegroups.com.

Re: [Extern] Re: [dspace-tech] Re: change localhost to the server ip when listening DSpace 7.4 !

[Israel Irizarry]

Hi everyone!

I am experiencing a similar issue. I do have https support for the UI and 
REST I believe. Here is the config.prod.yml portions and the local.cfg 
settings. I am using 7.6.
-
 
config.prod.yml
ui:
  ssl: false
  host: cuvault.cumberland.edu
  port: 4000
  # NOTE: Space is capitalized because 'namespace' is a reserved string in 
TypeScript
  nameSpace: /
  # The rateLimiter settings limit each IP to a 'max' of 500 requests per 
'windowMs' (1 minute).
  rateLimiter:
windowMs: 6 # 1 minute
max: 500 # limit each IP to 500 requests per windowMs
  # Trust X-FORWARDED-* headers from proxies (default = true)
  useProxies: true
rest:
  ssl: true
  host: cuvault.cumberland.edu
  port: 443
  nameSpace: /server
-
 
local.cfg
dspace.server.url = https://cuvault.cumberland.edu/server

dspace.ui.url = https://cuvault.cumberland.edu
rest.cors.allowed-origins = ${dspace.ui.url}
# Name of the site
dspace.name = DSpace at Cumberland University

I have tried so many different settings, but I keep getting an error 500 
when trying to access dspace on another computer in our network. It works 
on the server just fine. I am not sure if there is a setting I am missing 
or a configuration that I have wrong.
On Thursday, September 19, 2024 at 7:02:43 AM UTC-5 Michael Plate wrote:

> Hi,
>
> AFAIK DSpace 7+ does not run w/o HTTPS besides localhost.
>
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace
>
> "
> Production Installation (adding HTTPS support): Running the DSpace 
> Backend on HTTP & port 8080 is only usable for local development 
> environments (where you are running the UI and REST API from the same 
> machine, and only accessing them via localhost URLs). If you want to 
> run DSpace in Production, you MUST run the backend with HTTPS support 
> (otherwise logins will not work outside of your local domain).
> "
>
> Michael
>
>
> Am 19.09.24 um 13:46 schrieb Saad Itani:
> > same problem it loads the page (dspace ui) then it gives 500; ssl off
> > 
> > On Friday, July 26, 2024 at 11:51:31 AM UTC+3 suresh patil wrote:
> > 
> > Hi All,
> > 
> > anybody running DSpace 7.6.1 in the LAN through LAN IP without HTTPS?
> > 
> […]
>
>

-- 
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/14cbfae7-ea08-4be3-ac3b-1d6057616b16n%40googlegroups.com.

Re: [Extern] Re: [dspace-tech] Re: change localhost to the server ip when listening DSpace 7.4 !

[Israel Irizarry]

When I go to https://cuvault.cumberland.edu/server it loads just fine on an 
computer on our network. It seems to just be dspace's frontend ( 
https://cuvault.cumberland.edu ).

On Tuesday, October 8, 2024 at 11:54:23 AM UTC-5 Israel Irizarry wrote:

> Hi everyone!
>
> I am experiencing a similar issue. I do have https support for the UI and 
> REST I believe. Here is the config.prod.yml portions and the local.cfg 
> settings. I am using 7.6.
> -
>  
> config.prod.yml
> ui:
>   ssl: false
>   host: cuvault.cumberland.edu
>   port: 4000
>   # NOTE: Space is capitalized because 'namespace' is a reserved string in 
> TypeScript
>   nameSpace: /
>   # The rateLimiter settings limit each IP to a 'max' of 500 requests per 
> 'windowMs' (1 minute).
>   rateLimiter:
> windowMs: 6 # 1 minute
> max: 500 # limit each IP to 500 requests per windowMs
>   # Trust X-FORWARDED-* headers from proxies (default = true)
>   useProxies: true
> rest:
>   ssl: true
>   host: cuvault.cumberland.edu
>   port: 443
>   nameSpace: /server
> -
>  
> local.cfg
> dspace.server.url = https://cuvault.cumberland.edu/server
>
> dspace.ui.url = https://cuvault.cumberland.edu
> rest.cors.allowed-origins = ${dspace.ui.url}
> # Name of the site
> dspace.name = DSpace at Cumberland University
>
> I have tried so many different settings, but I keep getting an error 500 
> when trying to access dspace on another computer in our network. It works 
> on the server just fine. I am not sure if there is a setting I am missing 
> or a configuration that I have wrong.
> On Thursday, September 19, 2024 at 7:02:43 AM UTC-5 Michael Plate wrote:
>
>> Hi, 
>>
>> AFAIK DSpace 7+ does not run w/o HTTPS besides localhost. 
>>
>> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace 
>>
>> " 
>> Production Installation (adding HTTPS support): Running the DSpace 
>> Backend on HTTP & port 8080 is only usable for local development 
>> environments (where you are running the UI and REST API from the same 
>> machine, and only accessing them via localhost URLs). If you want to 
>> run DSpace in Production, you MUST run the backend with HTTPS support 
>> (otherwise logins will not work outside of your local domain). 
>> " 
>>
>> Michael 
>>
>>
>> Am 19.09.24 um 13:46 schrieb Saad Itani: 
>> > same problem it loads the page (dspace ui) then it gives 500; ssl off 
>> > 
>> > On Friday, July 26, 2024 at 11:51:31 AM UTC+3 suresh patil wrote: 
>> > 
>> > Hi All, 
>> > 
>> > anybody running DSpace 7.6.1 in the LAN through LAN IP without HTTPS? 
>> > 
>> […] 
>>
>>

-- 
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/3c20401c-c532-487a-9c29-85cf34f7a12en%40googlegroups.com.

[dspace-tech] Re: Not able to login [invalid email or password] on the front end

[Israel Irizarry]

Hello!

Were you ever able to solve this issue? I am experiencing the same thing.

Thanks!

On Saturday, September 2, 2023 at 10:55:58 PM UTC-5 Watson Anikwai wrote:

> I run into this issue where am not able to login on the frontend with my 
> email and password. I attached log files to see for tomcat and dspace.
>
> Any help will be appreciated.
>
>
> Regards,
> Watson
>

-- 
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/fb438f77-3d04-46c2-98ff-b9955f9fcdccn%40googlegroups.com.

Re: [dspace-tech] Re: 500 Service Unavailable in Dspace 7.6.1

[Israel Irizarry]

Hey everyone!

I am experiencing the same issue, but I cannot find the solution or cause. 
I have tried everything on the hints site, and I am still getting the 500 
error. Yarn test:rest comes out all good, my local.cfg and config.prod.yml 
files looks good, and I am running under HTTPS on both my /server and my UI 
sides. I know the problem has to do with the communication the frontend is 
having with the backend, but I cannot seem to find how to solve the issue. 
When checking the console in my browser, I do see the "No _links section 
found at..." error from User Interface, but when I add /server/api, all the 
links show up just fine. I have pinged the server and have fiddled around 
with all sorts of configurations, and nothing has worked. Any ideas?

Thanks!

On Tuesday, April 23, 2024 at 4:13:46 PM UTC-5 Abdellah Adghar wrote:

> Yes right.the problem is between backend and frontend.
>
> Le mar. 23 avr. 2024, 21:15, DSpace Technical Support <
> dspac...@googlegroups.com> a écrit :
>
>> Hi,
>>
>> Please also see our Troubleshooting Guide for DSpace 7 (and above): 
>> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>>
>> This 500 exception is a general error that is also documented in our 
>> "Common Installation Problems".  Usually it's a misconfiguration or 
>> communication issue between your UI and REST API.  See also the hints at 
>> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-%22500ServiceUnavailable%22fromtheUserInterface
>>
>> Tim
>>
>> -- 
>> 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/2e147a39-4cbe-4112-b8f7-c412ef7d575dn%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/ee989f9b-a243-496c-85c7-74179bc7bdefn%40googlegroups.com.

[dspace-tech] DOI Schema changed form 3 to 4.

[Jose Blanco]

I have a question about going from DOI schema 3 to 4.  I have put this
in place on our production site, and I'm finding that sometimes (not
always) if an item changes and a request to update it is sent to
DataCite, you get a failure, but if you make the request again a few
times, the request finally succeeds.  I changed 72 items the other day
and I think it took about 6  calls of  `./dspace doi-organiser -u `
for all 72 items to be updated and for failures to stop being
reported.  I can see in the doi table that the status for these items
went eventually from 6, to 3.  I wonder if anyone else has experienced
this and has a fix?

Thank you!
-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-t%2BB6-NBFmHiUE7-2rdALRfb%3DT3hLMdcJfG6gGpieb3AA%40mail.gmail.com.