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: <dspace-tech@googlegroups.com> on behalf of DCUOIT <dcuoi...@gmail.com> Date: Tuesday, June 23, 2020 at 11:28 AM To: DSpace Technical Support <dspace-tech@googlegroups.com> 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: <dspac...@googlegroups.com<javascript:>> on behalf of DCUOIT <dcuo...@gmail.com<javascript:>> Date: Tuesday, June 23, 2020 at 10:15 AM To: DSpace Technical Support <dspac...@googlegroups.com<javascript:>> 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<javascript:>. 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.
