[dspace-tech] Migration of DSpace-CRIS 5.10 to DSpace 7.6 (non-CRIS)

[Sean Carte]

I'm trying to migrate a DSpace-CRIS 5.10 instance to DSpace 7.6, but am
experiencing problems.

Doing a simple upgrade as in installing DSpace 7.6 on a new server and
copying the database across, then running dspace database migrate seems to
work, but `dspace index-discovery -b -f` results in a truncated Author
index and these errors appear in the log:

2024-04-24 15:08:48,726 ERROR org.dspace.discovery.SolrServiceImpl @ No
choices plugin was configured for  field "dc_contributor_author".
java.lang.IllegalArgumentException: No choices plugin was configured for
 field "dc_contributor_author".
at
org.dspace.content.authority.ChoiceAuthorityManager.getLabel(ChoiceAuthorityManag
er.java:261)
at
org.dspace.content.authority.ChoiceAuthorityManager.getLabel(ChoiceAuthorityManag
er.java:249)
at
org.dspace.browse.SolrBrowseCreateDAO.additionalIndex(SolrBrowseCreateDAO.java:215)
at
org.dspace.discovery.SolrServiceImpl.buildDocument(SolrServiceImpl.java:1424)
at
org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:230)
at
org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:410)
at
org.dspace.discovery.SolrServiceImpl.createIndex(SolrServiceImpl.java:370)
at org.dspace.discovery.IndexClient.main(IndexClient.java:117)
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:226)
at
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78)

I reported this on the dspace-cris Slack and the conclusion we arrived at
was that there is no migration path from CRIS to non-CRIS DSpace.

So I attempted to upgrade to DSpace-CRIS (2023.02.03). The upgrade
instructions are complicated, involving the use of Pentaho Kettle, with
which I am not familiar. As this procedure seems to be exclusively for
migrating CRIS attributes, I skipped it and tried to run the upgrade
without it. That went about as well as you can imagine.

So I exported the entire site as an AIP archive, but now I find that I
cannot import it. I have a fresh install of DSpace 7.6 with an
administrator user. I used the following command:
/dspace/bin/dspace packager -r -a -f -t AIP -e sean.ca...@gmail.com -i
10321/0 -o skipIfParentMissing=true sitewide-aip.zip

But receive the following error:
org.dspace.content.crosswalk.CrosswalkException:
org.dspace.content.packager.PackageException: Unable to translate Handle to
Internal ID in group named 'COLLECTION_hdl:10321/14_DEFAULT_READ' as DSpace
Object (Handle='hdl:10321/14') does not exist.
at
org.dspace.content.crosswalk.METSRightsCrosswalk.ingest(METSRightsCrosswalk.java:516)
at
org.dspace.content.crosswalk.METSRightsCrosswalk.ingest(METSRightsCrosswalk.java:425)
at
org.dspace.content.packager.METSManifest.crosswalkXmd(METSManifest.java:1128)
at
org.dspace.content.packager.METSManifest.crosswalkObjectOtherAdminMD(METSManifest.java:1048)
at
org.dspace.content.packager.AbstractMETSIngester.ingestObject(AbstractMETSIngester.java:447)
at
org.dspace.content.packager.AbstractMETSIngester.replace(AbstractMETSIngester.java:1075)
at
org.dspace.content.packager.AbstractPackageIngester.replaceAll(AbstractPackageIngester.java:275)
at
org.dspace.content.packager.AbstractPackageIngester.replaceAll(AbstractPackageIngester.java:303)
at
org.dspace.content.packager.AbstractPackageIngester.replaceAll(AbstractPackageIngester.java:303)
at
org.dspace.content.packager.AbstractPackageIngester.replaceAll(AbstractPackageIngester.java:303)
at org.dspace.app.packager.Packager.replace(Packager.java:684)
at org.dspace.app.packager.Packager.main(Packager.java:361)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:283)
at
org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:134)
at
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:99)
Caused by: org.dspace.content.packager.PackageException: Unable to
translate Handle to Internal ID in group named
'COLLECTION_hdl:10321/14_DEFAULT_READ' as DSpace Object
(Handle='hdl:10321/14') does not exist.
at
org.dspace.content.packager.PackageUtils.translateGroupNameForImport(PackageUtils.java:928)
  

Re: [dspace-tech] Adding Browse By Items

[Sean Carte]

Hi Lewatle

I'm not sure if it's the best way to do this, but I edit this file:
~/dspace-angular/src/assets/i18n/en.json5

You'll need to edit/add fields for browse.comcol.by, browse.metadata and
menu.section, e.g:

this adds the 'By Date Accessioned':
  "browse.comcol.by.dateaccessioned": "By Date Accessioned",
  "browse.metadata.dateaccessioned": "Date Accessioned",
  "browse.metadata.dateaccessioned.breadcrumbs": "Browse by Date
Accessioned",
  "menu.section.browse_community_by_dateaccessioned": "By Date Accessioned",
  "menu.section.browse_community_by_dateaccessioned": "By Date Accessioned",
  "menu.section.browse_global_by_dateaccessioned": "By Date Accessioned",

Then you'll need to rebuild and deploy.

Sean

On Fri, 16 Feb 2024 at 15:56, Lewatle Johannes Phaladi 
wrote:

> Hello Sean and DSpace Team,
>
> I have attached images detailing changes done up to now trying to
> customize browse by dc fields by adding preferred fields, in dspace.cfg I
> have added few fields and in en.json5 file also updated wording, only
> Department field is updated but not searching metadata related to
> dc.department, the only field that search correct metadata is dc date
> accessioned but its wording not appearing on the menu, By Dateaccessioned
> not visible on the menu.
>
> Is there any place where I should update to make this fields search
> metadata and show on frontend when user click them.
>
> Regards,
> Lewatle
>
> On Friday 12 January 2024 at 10:43:02 UTC+2 Lewatle Johannes Phaladi wrote:
>
>> Hello Sean,
>>
>> Thanks a lot, I will have a look at those comments as indicated.
>>
>> Regards,
>> Lewatle
>>
>> On Friday 12 January 2024 at 10:26:58 UTC+2 Sean Carte wrote:
>>
>>> Hi Lewatie
>>>
>>> You'll need to look at the webui.browse.index.* settings in your
>>> dspace.cfg file. The comments therein are helpful.
>>>
>>> Sean
>>>
>>> On Thu, 11 Jan 2024 at 14:35, Lewatle Johannes Phaladi <
>>> joem...@gmail.com> wrote:
>>>
>>>> Dear All,
>>>>
>>>> Please assist on how to add browse by items , I would like to add
>>>> department field on the following list. The first image below is browse by
>>>> from out of box DSpace software, the second picture shows added fields I
>>>> would like to edit DSpace 7.6 installation and put 1 or 2 more fields
>>>>
>>>> [image: browse by 1.png]
>>>>
>>>>
>>>>
>>>>
>>>> [image: browse by 2.png]
>>>>
>>>> Regards,
>>>> Lewatle
>>>>
>>>> --
>>>> 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/144c8a1f-49dd-47e0-87b5-f9bd4472b9abn%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/dspace-tech/144c8a1f-49dd-47e0-87b5-f9bd4472b9abn%40googlegroups.com?utm_medium=email_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/e84c2545-ceb8-4280-b2bf-266e3ff3a4b2n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/e84c2545-ceb8-4280-b2bf-266e3ff3a4b2n%40googlegroups.com?utm_medium=email_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/CA%2BxAuhP_vgQ%2B2%3DKLiLsOCYoh2uFrWm_%2BOdDyEnoaKP72yvW2ww%40mail.gmail.com.

Re: [dspace-tech] Adding Browse By Items

[Sean Carte]

Hi Lewatie

You'll need to look at the webui.browse.index.* settings in your dspace.cfg
file. The comments therein are helpful.

Sean

On Thu, 11 Jan 2024 at 14:35, Lewatle Johannes Phaladi 
wrote:

> Dear All,
>
> Please assist on how to add browse by items , I would like to add
> department field on the following list. The first image below is browse by
> from out of box DSpace software, the second picture shows added fields I
> would like to edit DSpace 7.6 installation and put 1 or 2 more fields
>
> [image: browse by 1.png]
>
>
>
>
> [image: browse by 2.png]
>
> Regards,
> Lewatle
>
> --
> 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/144c8a1f-49dd-47e0-87b5-f9bd4472b9abn%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/CA%2BxAuhPQNF%2Bkz6Hh31jGX-1fr1Rxjq_i0Jvq7e_3SJDBi-ENrg%40mail.gmail.com.

Re: [dspace-tech] Re: date.accessioned v. date.available

[Sean Carte]

Thanks for the info, Tim.

Sean

On Thu, 19 Oct 2023 at 21:39, DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> Hi Sean,
>
> This has been a discussion for some time. See this older thread:
> https://groups.google.com/g/dspace-tech/c/k7qCSJVhRrU
>
> There's also a ticket that describes the behavior in DSpace 7 here:
> https://github.com/DSpace/DSpace/issues/6583
>
> And, some recent work to fix the issue here:
> https://github.com/DSpace/DSpace/pull/9103  (This is under consideration
> for 8.0).
>
> To summarize: the "availability" time is no longer in metadata (in the new
> Embargo system, which is required in 7.x). Embargo related info is now only
> stored on the access policies (Edit Item -> Status -> Authorizations). More
> discussion also in this ticket:
> https://github.com/DSpace/DSpace/issues/9071
>
> Tim
>
> On Thursday, October 19, 2023 at 6:49:59 AM UTC-5 DSpace Technical Support
> wrote:
>
>> What is the difference between date.accessioned and date.available?
>>
>> According to the documentation:
>>
>> Once any workflow process is successfully and positively completed, the
>> InProgressSubmission object is consumed by an "item installer", that
>> converts the InProgressSubmission into a fully blown archived item in
>> DSpace. The item installer:
>> Assigns an accession date
>> Adds a "date.available" value to the Dublin Core metadata record of the
>> item
>> Adds an issue date if none already present
>>
>> And the metadata descriptions are as follows:
>> date accessioned¹ Date DSpace takes possession of item.
>> date available¹ Date or date range item became available to the public.
>>
>> But on the items I've checked, the date.accessioned and date.available
>> are identical. Even in items where the provenance shows three days between
>> submission and availability.
>>
>> I would have expected date.accessioned to be closer to the submission
>> date. But I suppose there's the date.submitted for that, though that
>> doesn't seem to be auto-populated.
>>
>> date
>>
>> submitted
>>
>> Recommend for theses/dissertations.
>> Is the description.provenance field the only way to determine the time
>> between submission and availability?
>>
>> 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/77c24370-fe19-435c-9330-21ad9900294en%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/CA%2BxAuhMgUUVhvNrEBmkkCepxAwVEWx87zc7sO59xVX3neenurQ%40mail.gmail.com.

[dspace-tech] date.accessioned v. date.available

[Sean Carte]

What is the difference between date.accessioned and date.available?

According to the documentation:

Once any workflow process is successfully and positively completed, the
InProgressSubmission object is consumed by an "item installer", that
converts the InProgressSubmission into a fully blown archived item in
DSpace. The item installer:
Assigns an accession date
Adds a "date.available" value to the Dublin Core metadata record of the item
Adds an issue date if none already present

And the metadata descriptions are as follows:
date accessioned¹ Date DSpace takes possession of item.
date available¹ Date or date range item became available to the public.

But on the items I've checked, the date.accessioned and date.available are
identical. Even in items where the provenance shows three days between
submission and availability.

I would have expected date.accessioned to be closer to the submission date.
But I suppose there's the date.submitted for that, though that doesn't seem
to be auto-populated.

date

submitted

Recommend for theses/dissertations.
Is the description.provenance field the only way to determine the time
between submission and availability?

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/CA%2BxAuhPF93Z-5S-xOr3FbhXCRzcvNXG5wQO_abH2%3DN0Bmm4S4g%40mail.gmail.com.

Re: [dspace-tech] Harvesting using OAI-PMH

[Sean Carte]

Once off, I suppose. It would be nice to be able to update the collection,
though.

Sean

On Wed, 21 Jun 2023 at 14:15, Mumanyi, Bravismore  wrote:

> I see...
> Is it a once off harvest or ongoing?
> [image: logo]
> *Bravismore Mumanyi*
> HOD: Systems and Training
> ILRC
> *University of Namibia*
> Tel: +264 61 206 3522
> Fax:
> E-mail: bmuma...@unam.na
> Web: http://www.unam.edu.na
> *Private* *Bag 13301, 340 Mandume Ndemufayo Ave, Pionierspark, Windhoek,
> NAMIBIA*
>
> --
> *From:* Sean Carte 
> *Sent:* 21 June 2023 14:12
> *To:* Mumanyi, Bravismore 
> *Cc:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] Harvesting using OAI-PMH
>
> Hi Bravismore
>
> It's not my repository that I'm harvesting.
>
> Sean
>
> On Wed, 21 Jun 2023 at 14:07, Mumanyi, Bravismore 
> wrote:
>
> Hi Sean
>
> Why not combine "in place" and then harvest?
>
> By either playing around with underlying parent-child tables or batch
> metadata editing tool.
> Thank you
>
> Regards
>
> --
> *From:* dspace-tech@googlegroups.com  on
> behalf of Sean Carte 
> *Sent:* 21 June 2023 10:40
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Harvesting using OAI-PMH
>
> Is it possible to harvest an existing repository's collections into a new
> repository so that multiple collections from different communities are
> combined in the new repository?
>
> For example:
>
> Existing repository collections:
> A
> B
> C
> D
>
> New repository collections:
> A & C
> B & D
>
> As far as I've been able to figure out, I can set a collection to harvest
> only a single set of records. I can't find a way to append another set.
>
> 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/CA%2BxAuhPwQhFCm4Bs9_Jr8x6rGttVq-Y0MP3pnu2LkYmiR6-Ytw%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhPwQhFCm4Bs9_Jr8x6rGttVq-Y0MP3pnu2LkYmiR6-Ytw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> CAUTION -EXTERNAL SENDER: Please be careful when opening links and
> attachments. UNAM Directorate: Information & Communication Technology
> Services (DICTS)
>
> CAUTION -EXTERNAL SENDER: Please be careful when opening links and
> attachments. UNAM Directorate: Information & Communication Technology
> Services (DICTS)
>
> --
> *From:* Sean Carte 
> *Sent:* 21 June 2023 14:12
> *To:* Mumanyi, Bravismore 
> *Cc:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] Harvesting using OAI-PMH
>
> Hi Bravismore
>
> It's not my repository that I'm harvesting.
>
> Sean
>
> On Wed, 21 Jun 2023 at 14:07, Mumanyi, Bravismore 
> wrote:
>
> Hi Sean
>
> Why not combine "in place" and then harvest?
>
> By either playing around with underlying parent-child tables or batch
> metadata editing tool.
> Thank you
>
> Regards
>
> --
> *From:* dspace-tech@googlegroups.com  on
> behalf of Sean Carte 
> *Sent:* 21 June 2023 10:40
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Harvesting using OAI-PMH
>
> Is it possible to harvest an existing repository's collections into a new
> repository so that multiple collections from different communities are
> combined in the new repository?
>
> For example:
>
> Existing repository collections:
> A
> B
> C
> D
>
> New repository collections:
> A & C
> B & D
>
> As far as I've been able to figure out, I can set a collection to harvest
> only a single set of records. I can't find a way to append another set.
>
> 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/CA%2BxAuhPwQhFCm4Bs9_Jr8x6rGttVq-Y0MP3pnu2LkYmiR6-Ytw%40mail.gmail.co

Re: [dspace-tech] Harvesting using OAI-PMH

[Sean Carte]

Hi Bravismore

It's not my repository that I'm harvesting.

Sean

On Wed, 21 Jun 2023 at 14:07, Mumanyi, Bravismore  wrote:

> Hi Sean
>
> Why not combine "in place" and then harvest?
>
> By either playing around with underlying parent-child tables or batch
> metadata editing tool.
> Thank you
>
> Regards
>
> --
> *From:* dspace-tech@googlegroups.com  on
> behalf of Sean Carte 
> *Sent:* 21 June 2023 10:40
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Harvesting using OAI-PMH
>
> Is it possible to harvest an existing repository's collections into a new
> repository so that multiple collections from different communities are
> combined in the new repository?
>
> For example:
>
> Existing repository collections:
> A
> B
> C
> D
>
> New repository collections:
> A & C
> B & D
>
> As far as I've been able to figure out, I can set a collection to harvest
> only a single set of records. I can't find a way to append another set.
>
> 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/CA%2BxAuhPwQhFCm4Bs9_Jr8x6rGttVq-Y0MP3pnu2LkYmiR6-Ytw%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhPwQhFCm4Bs9_Jr8x6rGttVq-Y0MP3pnu2LkYmiR6-Ytw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> CAUTION -EXTERNAL SENDER: Please be careful when opening links and
> attachments. UNAM Directorate: Information & Communication Technology
> Services (DICTS)
>

-- 
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%2BxAuhP6XGUTo_g3yFKtsAzWCqPNHg6Ztm1YzxOo1kR%3DZNvKFg%40mail.gmail.com.

[dspace-tech] Harvesting using OAI-PMH

[Sean Carte]

Is it possible to harvest an existing repository's collections into a new
repository so that multiple collections from different communities are
combined in the new repository?

For example:

Existing repository collections:
A
B
C
D

New repository collections:
A & C
B & D

As far as I've been able to figure out, I can set a collection to harvest
only a single set of records. I can't find a way to append another set.

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/CA%2BxAuhPwQhFCm4Bs9_Jr8x6rGttVq-Y0MP3pnu2LkYmiR6-Ytw%40mail.gmail.com.

Re: [dspace-tech] Handle server failing to start

[Sean Carte]

Hi Bravismore

It could be related to this:

https://groups.google.com/g/dspace-tech/c/PqjfA5mqG4w/m/QDEXYSWCAAAJ

This problem is related to the handle server after an upgrade of the JDK.
Dr Balnaves has released a patched handle server, which is available here:

https://release.prosentient.com.au/handle62/handle.jar.gz

What I did was:

download the handle.jar.gz: `wget
https://release.prosentient.com.au/handle62/handle.jar.gz`

unzip it: `gzip -d handle.jar.gz`
list all the instances of handle-6.2.jar in /dspace/webapps: `find /dspace/
-name handle-6.2.jar`
copy the new handle.jar over them: e.g.: `cp handle.jar
/dspace/lib/handle-6.2.jar`
restart the handle server: `#systemctl restart handled.service`
check the log: `tail -f /dspace/log/handle-server.log`

Sean

On Wed, 24 May 2023 at 15:27, Mumanyi, Bravismore  wrote:

> Dear Dspace Community
>
> I am still on Dspace 6.3 and my handle server is failing to start.
> All I get from the handle error log is:
>
> *"2023/05/24 03:09:01 CAT" 25 Started new run.*
> *java.lang.UnsupportedOperationException*
> *at java.lang.Runtime.runFinalizersOnExit(Runtime.java:287)*
> *at java.lang.System.runFinalizersOnExit(System.java:1059)*
> *at net.handle.server.Main.initialize(Main.java:124)*
> *at net.handle.server.Main.main(Main.java:75)*
> *Shutting down...*
>
> I have tried re-generating the config with no success.
>
> Any pointers?
> [image: logo]
> *Bravismore Mumanyi*
> HOD: Systems and Training
> ILRC
> *University of Namibia*
> Tel: +264 61 206 3522
> Fax:
> E-mail: bmuma...@unam.na
> Web: http://www.unam.edu.na
> *Private* *Bag 13301, 340 Mandume Ndemufayo Ave, Pionierspark, Windhoek,
> NAMIBIA*
>
>
>
> 
>
> --
> 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/PA4PR04MB76002FFA0F958ED68234B319C4419%40PA4PR04MB7600.eurprd04.prod.outlook.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/CA%2BxAuhNb8n%2BEg9R2xCtTBqX4dpKw%3DWy4J%3DjzwJNTZVovFOHa7w%40mail.gmail.com.

Re: [dspace-tech] Is it possible rsync an assetstore between current and new servers

[Sean Carte]

For what it's worth, that's exactly what I would do.

Sean

On Thu, 18 May 2023 at 18:08, cpgr...@gmail.com  wrote:

> We are planning to do a test of moving our dspace 5 production server to
> dspace 7. Our sysadmin suggested we do an rsync of the assetstore so that
> the data could be transferred gradually and only a final copy done on the
> day we had been planning to do a full copy of the assetstore. The full copy
> would necessitate stopping tomcat on both servers, but would an rsync allow
> us to do most of the copying while the production server was still live and
> just shutdown both instances of tomcat briefly to finish the copy and
> ensure that we get the current state of the assetstore along with the
> export of the PostgreSQL database on the day we do the final migration?
>
> --
> 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/86d0810c-b37e-44cd-90b2-e226c59a1e7dn%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/CA%2BxAuhORnrWJ4Q-%2BhZO-Av5wihLcu1szD%3D-Q0rpfiWT5hABrVw%40mail.gmail.com.

Re: [dspace-tech] Migrating sharded SOLR statistics to DSPACE 7.4

[Sean Carte]

On Thu, 16 Feb 2023 at 15:42, Mark H. Wood  wrote:

> On Thu, Feb 16, 2023 at 09:41:25AM +0200, Sean Carte wrote:
> > On the Slack tech-support channel, Nicholas Woodward reported that he had
> > recreated the cores 'by copying the new statistics core into a new Solr
> > configset, e.g. statistics-2022, for each previous year and changing the
> > schema name in schema.xml. Then after restarting Solr I was able to
> import
> > all of the old stats CSV files.'
> >
> > I was about to try this, when I realised I'd made a mistake and imported
> > all my sharded statistics into the main core. I'm actually fine with
> that,
> > unless someone here tells me that that was a terrible thing to do.
>
> That's actually what the upgrade procedure ought to do, because
> sharding was not included when working out the separation of Solr from
> the DSpace build (which was required by changes in the packaging of
> currently supported Solr versions).  There may be a way to make it
> work, but the tools that currently come with DSpace will not help.
>
> Sharding is awaiting some discussion:
>
> o  Does sharding actually help?
>
> o  Consider that we are abusing a feature which was meant for
>evenly spreading load across multiple hosts.
>
> o  This could be done much more simply and organically, without
>involving DSpace code at all, using Time Routed Aliases, but TRA
>requires Solr Cloud, which runs a bit differently.  Is the benefit
>of sharding (whatever that actually is) worth the trouble to set up
>a (possibly degenerate) Cloud?
>
> --
> Mark H. Wood
>

Thanks, Mark. That's good to know. And it certainly makes my life easier
having everything in a single core.

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/CA%2BxAuhM2B23k%3DTZtd0cG4JQnxPaz96FFi5cTXnFS%3DEbodC4tRA%40mail.gmail.com.

Re: [dspace-tech] Migrating sharded SOLR statistics to DSPACE 7.4

[Sean Carte]

Hi Tuan

On the Slack tech-support channel, Nicholas Woodward reported that he had
recreated the cores 'by copying the new statistics core into a new Solr
configset, e.g. statistics-2022, for each previous year and changing the
schema name in schema.xml. Then after restarting Solr I was able to import
all of the old stats CSV files.'

I was about to try this, when I realised I'd made a mistake and imported
all my sharded statistics into the main core. I'm actually fine with that,
unless someone here tells me that that was a terrible thing to do.

Sean

On Tue, 14 Feb 2023 at 14:53, amtuan...@gmail.com 
wrote:

> Hi all
>
> We are in the process of migrating our DSpace 6x to 7.4.
>
> I am running into a problem with trying to import the SOLR statistics CSV
> files. We have our statistics sharded for each year and dumped the data to
> CSV files. However, the upgrade instructions have no mention of how to
> recreate the shards for statistics, only instructions for importing the
> CSVs. When I try to import the shards, I get the error 404 because the
> cores/shards are not created yet. Could you please give me some hints how
> to do this?
>
> Thanks for you help.
> Tuan
>
> https://wiki.lyrasis.org/display/DSDOC7x/Upgrading+DSpace
>
> Excerpt of the instructions I  followed below:
>
> Load authority and statistics from the dumps
> 
>  that
> you made earlier (not the disaster-recovery backup).
>
> [dspace]/bin/dspace solr-import-statistics -i authority
> [dspace]/bin/dspace solr-import-statistics -i statistics
>
> This could take quite some time.
>
> *If you had sharded your statistics, you will need to load the dump of
> each shard separately.  As when dumping, the index names will be ...
> statistics-2017 statistics-2018 statistics.*
>
> --
> 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/e2cc11bc-1761-4936-8a15-5895b3741340n%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/CA%2BxAuhM2EWcWn-05HU67xoCbAoJ7hqgJSugcfevYdtuzt9ymnQ%40mail.gmail.com.

Re: [dspace-tech] Issue with database migration 6.3 to 7.4

[Sean Carte]

Hi Jacob

I had a similar problem with a database I was trying to import: many /N
invalid commands. I gave my user superuser privileges and was able to
import the dump without those errors.

Sean

On Thu, 26 Jan 2023 at 23:06, Cameron, Jacob  wrote:

> Hi Everyone,
>
> I exported my DSpace 6.3 database, imported it on the new server running
> 7.4.  There were thousands of invalid command /N that showed up during the
> import and lots of other ERROR: relation "xxx" does not exist.
>
> I did try running dspace database migrate ignored afterwards and was given
> some errors.
>
> I checked the DSpace log and there was some messaged about being unable to
> find the bean by name or database but that may have been when I deleted my
> old database before recreating the new one to import to.
>
> Any thoughts or suggestions would be welcome.  I've seen a few suggestions
> out there and I've tried them, but I haven't had any luck.
>
> C:\DSpace\bin>dspace database migrate ignored
> Using DSpace installation in: C:\DSpace
>
> Database URL: jdbc:postgresql://localhost:5432/dspace
> Migrating database to latest version AND running previously "Ignored"
> migrations... (Check logs for details)
> Migration exception:
> java.sql.SQLException: Flyway migration error occurred
> at
> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:785)
> at
> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:672)
> at
> org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:195)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:277)
> at
> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:133)
> at
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98)
> Caused by:
> org.flywaydb.core.internal.command.DbMigrate$FlywayMigrateException:
> Migration
> V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql
> failed
>
> -
> SQL State  : 42703
> Error Code : 0
> Message: ERROR: column "resource_type_id" does not exist
> Location   :
> org/dspace/storage/rdbms/sqlmigration/postgres/V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql
> (C:\DSpace\file:\C:\DSpace\lib\dspace-api-7.4.jar!\org\dspace\storage\rdbms\sqlmigration\postgres\V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql)
> Line   : 16
> Statement  : CREATE INDEX metadatavalue_resource_type_id_idx ON
> metadatavalue (resource_type_id)
>
> at
> org.flywaydb.core.internal.command.DbMigrate.doMigrateGroup(DbMigrate.java:385)
> at
> org.flywaydb.core.internal.command.DbMigrate.lambda$applyMigrations$1(DbMigrate.java:275)
> at
> org.flywaydb.core.internal.jdbc.TransactionalExecutionTemplate.execute(TransactionalExecutionTemplate.java:55)
> at
> org.flywaydb.core.internal.command.DbMigrate.applyMigrations(DbMigrate.java:274)
> at
> org.flywaydb.core.internal.command.DbMigrate.migrateGroup(DbMigrate.java:247)
> at
> org.flywaydb.core.internal.command.DbMigrate.lambda$migrateAll$0(DbMigrate.java:141)
> at
> org.flywaydb.core.internal.database.postgresql.PostgreSQLAdvisoryLockTemplate.execute(PostgreSQLAdvisoryLockTemplate.java:69)
> at
> org.flywaydb.core.internal.database.postgresql.PostgreSQLConnection.lock(PostgreSQLConnection.java:99)
> at
> org.flywaydb.core.internal.schemahistory.JdbcTableSchemaHistory.lock(JdbcTableSchemaHistory.java:139)
> at
> org.flywaydb.core.internal.command.DbMigrate.migrateAll(DbMigrate.java:141)
> at
> org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:98)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:173)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:124)
> at
> org.flywaydb.core.FlywayExecutor.execute(FlywayExecutor.java:214)
> at org.flywaydb.core.Flyway.migrate(Flyway.java:124)
> at
> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:772)
> ... 9 more
> Caused by: org.flywaydb.core.internal.sqlscript.FlywaySqlScriptException:
> Migration
> V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql
> failed
>
> -
> SQL State  : 42703
> Error Code : 0
> Message: ERROR: column "resource_type_id" does not exist
> Location   :
> 

Re: [dspace-tech] Re: handle server quits after ubuntu upgrade

[Sean Carte]

Thank you for this, Edmund!

Sean

On Tue, 15 Nov 2022 at 00:58, Edmund Balnaves 
wrote:

> The compiled handle.jar file is available at
> https://release.prosentient.com.au/handle62/handle.jar.gz
> It can be used to replace the handle-6.2.jar reference in the dspace 6.4
> build or copied directly to the target directly to the target directories -
> particularly of course lib
>
> ./lib/handle-6.2.jar
> ./webapps/jspui/WEB-INF/lib/handle-6.2.jar
> ./webapps/xmlui/WEB-INF/lib/handle-6.2.jar
> ./webapps/swordv2/WEB-INF/lib/handle-6.2.jar
> ./webapps/rdf/WEB-INF/lib/handle-6.2.jar
> ./webapps/rest/WEB-INF/lib/handle-6.2.jar
> ./webapps/sword/WEB-INF/lib/handle-6.2.jar
> ./webapps/oai/WEB-INF/lib/handle-6.2.jar
>
> I have shared the build source at
> https://release.prosentient.com.au/handle62/handle6.2patched.tar.gz
>
> The base is hdl 6.2.05 code from handle.net
>
> Note that this does not contain the cnriutil references.
>
> I compiled lib/cnriutil.jar derived from the classes in the dspace version
> of handle-6.2.jar
>
> To achieve a distribution I modified the build.xml to remove references to
> the admintools. I'm guessing this must have been done before with the
> dspace distro.
>
> I modified
> ./net/handle/server/Main.java
> to remove System.runFinalizersOnExit(true);
>
> Further work could be done to replace this with an alternative code
> Runtime.addShutdownHook(new Runnable() {
> public void run(){
> // do whatever handle.net needs to exit cleaning on error();
> }
> });
>
> However I have tested the above simple change successfully in an updated
> ubuntu server running the dspace handle resolver.
> Not tested for long term service operation, so there is a risk the above
> change might lead to some memory leakage. However the fact that the handle
> service runs seperately makes it easy to monitor.
>
> The build process is:
> ant clean
> ant server
> ant distjar
>
> The build output is in the dist folder
>
> Hope this helps.
>
> Edmund
>
>
> On Tuesday, November 15, 2022 at 2:03:43 AM UTC+11 cpgr...@gmail.com
> wrote:
>
>> Thank you for your message.
>>
>> We are considering rolling back our server to Nov 10th when the Ubuntu
>> upgrade happened. Your fixed jar file would be a better quick fix.
>> Would you please send me a copy of the jar file and where I should put
>> it? I notice multiple copies of that jar all over the server and I don't
>> know which one it is crucial to replace and what to do to make it active.
>>
>> On Saturday, November 12, 2022 at 6:36:46 AM UTC-5 edmund@gmail.com
>> wrote:
>>
>>> This is a problem with the latest release of java (openjdk version
>>> "1.8.0_352").  It has now removed the deprecated class runFinalizersOnExit
>>>
>>> This class is used by the embedded handle.net jar classes to provide
>>> the resolver functions for the handle server.
>>>
>>> This is distributed via the maven libraries.There is testing going
>>> on upgraded to use a later handle.net distribution.
>>>
>>> I have tested a working alternative by rebuilding handle-6.2.jar with a
>>> minor change to ./net/handle/server/Main.java to comment out the now
>>> discontinued class at line 124
>>> //System.runFinalizersOnExit(true);
>>>
>>> After rebuild the handle jar and replacing it in the target directories,
>>> the Handle server starts successfully and I have tested with a live
>>> configuration - handle resolving completes successfuling.
>>>
>>> This could provide alternative for some to get a server live.
>>>
>>> Happy to share the build to project the above jar and/or the jar itself
>>>
>>> Gives us a fall-back solution at least.  Hopefully formal fix will be
>>> out soon.
>>>
>>> On Saturday, November 12, 2022 at 3:17:40 AM UTC+11 cpgr...@gmail.com
>>> wrote:
>>>
 We did an upgrade to Ubuntu last night and now our handle server quits
 immediately on trying to start it. Unfortunately, the person who set up
 our handle server has left our organization.

 Our handle-server.log reports:

 "2022/11/11 10:27:43 EST" 25 Rotating log files
 Error: null
 (see the error log for details.)

 Shutting down...

 and the error.log reports:

 "2022/11/11 10:27:43 EST" 25 Started new run.
 java.lang.UnsupportedOperationException
  at java.lang.Runtime.runFinalizersOnExit(Runtime.java:287)
  at java.lang.System.runFinalizersOnExit(System.java:1059)
  at net.handle.server.Main.initialize(Main.java:124)
  at net.handle.server.Main.main(Main.java:75)
 Shutting down...

 Can anyone help with what is going wrong or how to diagnose this
 further?
>>>
>>> --
> 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
> 

Re: [dspace-tech] Harvesting error

[Sean Carte]

This thread also refers to the problem, and explains a bit of the why, with
a potential solution:

https://groups.google.com/d/msgid/dspace-tech/bdb7534c-eb49-4bc0-8c3b-7ef2eb170c17n%40googlegroups.com?utm_medium=email_source=footer

Sean

On Wed, 24 Aug 2022 at 13:59, Sean Carte  wrote:

> Hi Ezequiel
>
> When I've encountered this sort of problem it's always been problematic
> characters in the abstract.
>
> Have a look at:
>
>
> https://repositorio.uca.edu.ar/oai/request?verb=ListRecords=oai_dc///com_123456789_719/7000
>
> In the 'root cause' of the exception, you'll find this:
>
> Contenido: Biblical archaeology and the emergence of the 
> kingdom of Edom / Nadav Na’Aman -- Will womankind now go hunting? 
> Constructions of gender in the Aqhat Epic / Eric D. McDonell  Jr. -- The 
> reward of the pharaohs: Egyptian royal grants and gifts for the rulers of 
> Canaan in the Amarna letters / Mohy Eldin E. Abo-Eleaz -- The toponym 
> ᵁᴿᵁ---ℎ̮
>  in the letters RSO 23 28-35 and elsewhere / Eduardo Torrecilla --Why 
> jews can also be called israelites. A new approach to the question of 
> “Biblical Israel” / Wolfgang Schütte -- La (re)creación del mito de Mitra / 
> Jaime Alvar Ezquerra -- Cartago y Alejandro. El problemático rastreo de unas 
> relaciones / Christian San José Campos -- Los small finds de Tell el-Ghaba 
> (Sinaí septentrional, Egipto): una revisión / Eva Amanda Calomino --  
> Nessana necropoleis: An aerial and ground survey of Byzantine era cemeteries 
> in the israeli Negev / Pablo Betzer -- ¿Libertad sexual o prostitución? 
> Reflexiones acerca de la relación entre mujeres y sexualidad en los estudios 
> históricos / Agnès Garcia-Ventura -- Reseñas bibliográficas
>
> I suspect it's those characters that have not rendered correctly that have
> caused the error:
>
> ... 
> ᵁᴿᵁ---ℎ̮
>  ...
>
>
> This is in the abstract of
> https://repositorio.uca.edu.ar/handle/123456789/14552.
>
> That kind of answers the what, but not the why; I hope it is of some use.
>
> Sean
>
> On Tue, 23 Aug 2022 at 22:38, Ezequiel Esposito <
> espositoezequ...@gmail.com> wrote:
>
>> Dear sirs,
>>
>> EBSCO told us that there was a problem with the harvest of our
>> repository. They send us the following error:
>>
>> ERROR: Could not harvest from https://repositorio.uca.edu.ar/oai/request:
>> Error while harvesting using setSpec 'com_123456789_719'
>>
>> It is possible the error is in here:
>> https://repositorio.uca.edu.ar/handle/123456789/719 but I don't know
>> what is the problem.
>>
>> ¿Could you help me? Thanks.
>>
>> Ezequiel Esposito
>>
>> --
>> 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/e12abf36-7a8c-4738-bb2d-d99e2f3c089an%40googlegroups.com
>> <https://groups.google.com/d/msgid/dspace-tech/e12abf36-7a8c-4738-bb2d-d99e2f3c089an%40googlegroups.com?utm_medium=email_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/CA%2BxAuhMwx%3D1gWWjfYOQr8pD-7yHQrB3MH7i3msEKO%2B46uqVkQA%40mail.gmail.com.

Re: [dspace-tech] Harvesting error

[Sean Carte]

Hi Ezequiel

When I've encountered this sort of problem it's always been problematic
characters in the abstract.

Have a look at:

https://repositorio.uca.edu.ar/oai/request?verb=ListRecords=oai_dc///com_123456789_719/7000

In the 'root cause' of the exception, you'll find this:

Contenido: Biblical archaeology and the emergence of
the kingdom of Edom / Nadav Na’Aman -- Will womankind now go hunting?
Constructions of gender in the Aqhat Epic / Eric D. McDonell  Jr. --
The reward of the pharaohs: Egyptian royal grants and gifts for the
rulers of Canaan in the Amarna letters / Mohy Eldin E. Abo-Eleaz --
The toponym 
ᵁᴿᵁ---ℎ̮
in the letters RSO 23 28-35 and elsewhere / Eduardo Torrecilla --   Why
jews can also be called israelites. A new approach to the question of
“Biblical Israel” / Wolfgang Schütte -- La (re)creación del mito de
Mitra / Jaime Alvar Ezquerra -- Cartago y Alejandro. El problemático
rastreo de unas relaciones / Christian San José Campos -- Los small
finds de Tell el-Ghaba (Sinaí septentrional, Egipto): una revisión /
Eva Amanda Calomino --  Nessana necropoleis: An aerial and ground
survey of Byzantine era cemeteries in the israeli Negev / Pablo Betzer
--  ¿Libertad sexual o prostitución? Reflexiones acerca de la relación
entre mujeres y sexualidad en los estudios históricos / Agnès
Garcia-Ventura -- Reseñas bibliográficas

I suspect it's those characters that have not rendered correctly that have
caused the error:

... 
ᵁᴿᵁ---ℎ̮
...


This is in the abstract of
https://repositorio.uca.edu.ar/handle/123456789/14552.

That kind of answers the what, but not the why; I hope it is of some use.

Sean

On Tue, 23 Aug 2022 at 22:38, Ezequiel Esposito 
wrote:

> Dear sirs,
>
> EBSCO told us that there was a problem with the harvest of our repository.
> They send us the following error:
>
> ERROR: Could not harvest from https://repositorio.uca.edu.ar/oai/request:
> Error while harvesting using setSpec 'com_123456789_719'
>
> It is possible the error is in here:
> https://repositorio.uca.edu.ar/handle/123456789/719 but I don't know what
> is the problem.
>
> ¿Could you help me? Thanks.
>
> Ezequiel Esposito
>
> --
> 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/e12abf36-7a8c-4738-bb2d-d99e2f3c089an%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/CA%2BxAuhObDBquKVBRa0xte55RiUPgaiitHQhvrB1bWXDy0%3DmDgw%40mail.gmail.com.

[dspace-tech] OAI listRecords vs UI Publications

[Sean Carte]

Should the number of records provided by OAI match the number of
publications provided by the UI?

If I use ListRecords for OAI:

/oai/request?verb=ListRecords=oai_dc

I get 1530 results,

but, the UI reports 3872 publications.

I don't see any errors when I browse the OAI list of records.

Something seems wrong here, but I don't know what to do about it.

Sean

DSpace version:  CRIS-5.10.0-SNAPSHOT
  SCM revision:  67e7d010e7eda86925980b2a43581b9d4f4929a3
SCM branch:  dspace-5_x_x-cris
OS:  Linux(amd64) version 4.4.0-229-generic
  Applications:
 Discovery:  enabled.
   JRE:  Private Build version 1.8.0_312
   Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20 2018
 Maven version:  3.3.9

-- 
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%2BxAuhPyjPm-ELEoPmbG__8LWGgamKmWJG5tHWn3UGnKQy9DwA%40mail.gmail.com.

[dspace-tech] Re: Error when trying to move an item

[Sean Carte]

To follow up, what I did was export the items using AIP, then I restored
them.

Sean

On Wed, 20 Jul 2022 at 13:10, Sean Carte  wrote:

> I'm getting an error when trying to move two items that have been
> submitted to a temporary collection. I've copied the error from the log
> below.
>
> All other admin actions appear to work, but 'Move Item' results in the
> error message below. Other items submitted to this collection do not cause
> this error.
>
> Short of deleting the items and resubmitting, is there anything I can do
> to change the items' collection?
>
> 2022-07-20 12:42:46,911 WARN
>  org.dspace.app.webui.servlet.InternalErrorServlet @
> :session_id=1004CF3D79481D7505D39F83C451AF66:internal_error:-- URL Was:
> https://openscholar.dut.ac.za/tools/edit-item
> -- Method: POST
> -- Parameters were:
> -- item_id: "4744"
> -- action: "7"
> -- submit: "Move Item"
>
> java.lang.ArrayIndexOutOfBoundsException: 16
> at org.dspace.content.Item.getCollectionsNotLinked(Item.java:1849)
> at
> org.dspace.app.webui.servlet.admin.EditItemServlet.doDSPost(EditItemServlet.java:277)
> at
> org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:115)
> at org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:73)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
> at
> org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnlyFilter.java:66)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
> at
> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:494)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
> at psiprobe.Tomcat80AgentValve.invoke(Tomcat80AgentValve.java:35)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
> at
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522)
> at
> org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:868)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:672)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1520)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1476)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:748)
>
> DSpace version:  CRIS-5.10.0-SNAPSHOT
>   SCM revision:  67e7d010e7eda86925980b2a43581b9d4f4929a3
> SCM branch:  dspace-5_x_x-cris
> OS:  Linux(amd64) version 4.4.0-229-generic
>   Applications:
>  Discovery:  enabled.
>JRE:  Private Build version 1.8.0_312
>Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20 2018
>  Maven version:  3.3.9
>
> 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/CA%2BxAuhOCW-3jk1nAQw__3qDX13v3krznzGr2PurLT-DwgcLesw%40mail.gmail.com.

[dspace-tech] Error when trying to move an item

[Sean Carte]

I'm getting an error when trying to move two items that have been submitted
to a temporary collection. I've copied the error from the log below.

All other admin actions appear to work, but 'Move Item' results in the
error message below. Other items submitted to this collection do not cause
this error.

Short of deleting the items and resubmitting, is there anything I can do to
change the items' collection?

2022-07-20 12:42:46,911 WARN
 org.dspace.app.webui.servlet.InternalErrorServlet @
:session_id=1004CF3D79481D7505D39F83C451AF66:internal_error:-- URL Was:
https://openscholar.dut.ac.za/tools/edit-item
-- Method: POST
-- Parameters were:
-- item_id: "4744"
-- action: "7"
-- submit: "Move Item"

java.lang.ArrayIndexOutOfBoundsException: 16
at org.dspace.content.Item.getCollectionsNotLinked(Item.java:1849)
at
org.dspace.app.webui.servlet.admin.EditItemServlet.doDSPost(EditItemServlet.java:277)
at
org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:115)
at org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at
org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnlyFilter.java:66)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:494)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
at psiprobe.Tomcat80AgentValve.invoke(Tomcat80AgentValve.java:35)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522)
at
org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:868)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:672)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1520)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1476)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

DSpace version:  CRIS-5.10.0-SNAPSHOT
  SCM revision:  67e7d010e7eda86925980b2a43581b9d4f4929a3
SCM branch:  dspace-5_x_x-cris
OS:  Linux(amd64) version 4.4.0-229-generic
  Applications:
 Discovery:  enabled.
   JRE:  Private Build version 1.8.0_312
   Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20 2018
 Maven version:  3.3.9

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/CA%2BxAuhOd4Zha42DHXPLEfeSnFB59BaZHCTGtUxaNMHLchpj1tg%40mail.gmail.com.

Re: [dspace-tech] Duplicate key after restoring server from AIP backup

[Sean Carte]

Thanks, Tim.

I added a comment to
https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore

Sean

On Thu, 14 Jul 2022 at 19:41, Tim Donohue  wrote:

> Hi Sean,
>
> The "[dspace]/etc/" folder was removed in DSpace 7 because all the old SQL
> scripts (which used to sit in "etc" in older versions of DSpace) have been
> moved elsewhere.  This folder was already "mostly" empty in DSpace 5 & 6,
> and we completely emptied it out & removed it in DSpace 7.
>
>- SQL migration scripts (which used to be in that folder in 4.x or
>below) were all migrated to
>
> https://github.com/DSpace/DSpace/tree/main/dspace-api/src/main/resources/org/dspace/storage/rdbms/sqlmigration/postgres,
>as they are all now controlled by Flyway DB (as of DSpace 5.x)
>- The old "update-sequences.sql" SQL script (which used to be in that
>folder in 5.x or 6.x) has been replaced by the "./dspace database
>update-sequences" command
>
> So, if you see a "[dspace]/etc" folder, it can be safely removed after you
> upgrade to DSpace 7.  Any SQL scripts in that folder are outdated and
> unnecessary in DSpace 7.
>
> Tim
> --
> *From:* dspace-tech@googlegroups.com  on
> behalf of Sean Carte 
> *Sent:* Thursday, July 14, 2022 9:53 AM
> *To:* Michael Plate 
> *Cc:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] Duplicate key after restoring server from
> AIP backup
>
> Thanks for the advice, Michael.
>
> I do wonder, though, why the /dspace/etc/ directory is missing in 7.x? It
> doesn't seem to be there in:
> https://github.com/DSpace/DSpace/tree/main/dspace
>
> I took a copy from a 6.x installation, and ran it with psql. Apart from a
> couple of errors, it seemed to work and I can now deposit items.
>
> ERROR:  relation "workflowitem" does not exist
> LINE 1: ...setval('workflowitem_seq', max(workflow_id)) FROM workflowit...
>  ^
> ERROR:  relation "tasklistitem" does not exist
> LINE 1: ...setval('tasklistitem_seq', max(tasklist_id)) FROM tasklistit...
>
> Sean
>
> On Thu, 14 Jul 2022 at 12:48, Michael Plate <
> pl...@bibliothek.uni-kassel.de> wrote:
>
> Hi Sean,
>
> at least this you might correct this by setting the handle_seq to a
> value greater than the last handle.
> I don't recommend that for important systems :)
>
> Michael
>
>
> Am 14.07.22 um 08:02 schrieb Sean Carte:
> > I restored an entire site from an AIP backup, and now, when I attempt to
> > submit an item, I get this error:
> >
> > Caused by: java.sql.BatchUpdateException: Batch entry 0 update
> > public.handle set
> > resource_id='26a7cedb-76e7-4acc-a515-37708a3e1c7b'::uuid,
> > handle='123456789/9', resource_type_id=2 where handle_id=264 was
> > aborted: ERROR: duplicate key value violates unique constraint
> > "handle_handle_key"
> >Detail: Key (handle)=(123456789/9) already exists.  Call
> > getNextException to see other errors in the batch.
> >
> > I think this is because I haven't run the update-sequences.sql that the
> > documentation suggests I should, but I can't find that script; there
> > isn't even a /dspace/etc/ directory:
> >
> > ls /dspace/
> > assetstore  exportslog   solr upload
> > bin handle-server  reports   temp var
> > config  libsitemaps  triplestore  webapps
> >
> > This is the documentation I've been using:
> >
> >
> https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore#AIPBackupandRestore-RestoringEntireSite
> > <
> https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore#AIPBackupandRestore-RestoringEntireSite
> >
> >
> > DSpace version:  7.3-SNAPSHOT
> >SCM revision:  e5f316c9adf78e59d8277a271a0fc2a2d21da0f8
> >  SCM branch:  main
> >  OS:  Linux(amd64) version 5.4.0-120-generic
> >Applications:
> >   Discovery:  enabled.
> > JRE:  Private Build version 11.0.15
> > Ant version:  Apache Ant(TM) version 1.10.7 compiled on October 24
> 2019
> >   Maven version:  3.6.3
> > DSpace home:  /dspace
> >
> > Sean
> >
> > --
> > All messages to this mailing list should adhere to the Code of Conduct:
> > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> > <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&quo

Re: [dspace-tech] Duplicate key after restoring server from AIP backup

[Sean Carte]

Thanks for the advice, Michael.

I do wonder, though, why the /dspace/etc/ directory is missing in 7.x? It
doesn't seem to be there in:
https://github.com/DSpace/DSpace/tree/main/dspace

I took a copy from a 6.x installation, and ran it with psql. Apart from a
couple of errors, it seemed to work and I can now deposit items.

ERROR:  relation "workflowitem" does not exist
LINE 1: ...setval('workflowitem_seq', max(workflow_id)) FROM workflowit...
 ^
ERROR:  relation "tasklistitem" does not exist
LINE 1: ...setval('tasklistitem_seq', max(tasklist_id)) FROM tasklistit...

Sean

On Thu, 14 Jul 2022 at 12:48, Michael Plate 
wrote:

> Hi Sean,
>
> at least this you might correct this by setting the handle_seq to a
> value greater than the last handle.
> I don't recommend that for important systems :)
>
> Michael
>
>
> Am 14.07.22 um 08:02 schrieb Sean Carte:
> > I restored an entire site from an AIP backup, and now, when I attempt to
> > submit an item, I get this error:
> >
> > Caused by: java.sql.BatchUpdateException: Batch entry 0 update
> > public.handle set
> > resource_id='26a7cedb-76e7-4acc-a515-37708a3e1c7b'::uuid,
> > handle='123456789/9', resource_type_id=2 where handle_id=264 was
> > aborted: ERROR: duplicate key value violates unique constraint
> > "handle_handle_key"
> >Detail: Key (handle)=(123456789/9) already exists.  Call
> > getNextException to see other errors in the batch.
> >
> > I think this is because I haven't run the update-sequences.sql that the
> > documentation suggests I should, but I can't find that script; there
> > isn't even a /dspace/etc/ directory:
> >
> > ls /dspace/
> > assetstore  exportslog   solr upload
> > bin handle-server  reports   temp var
> > config  libsitemaps  triplestore  webapps
> >
> > This is the documentation I've been using:
> >
> >
> https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore#AIPBackupandRestore-RestoringEntireSite
> > <
> https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore#AIPBackupandRestore-RestoringEntireSite
> >
> >
> > DSpace version:  7.3-SNAPSHOT
> >SCM revision:  e5f316c9adf78e59d8277a271a0fc2a2d21da0f8
> >  SCM branch:  main
> >  OS:  Linux(amd64) version 5.4.0-120-generic
> >Applications:
> >   Discovery:  enabled.
> > JRE:  Private Build version 11.0.15
> > Ant version:  Apache Ant(TM) version 1.10.7 compiled on October 24
> 2019
> >   Maven version:  3.6.3
> > DSpace home:  /dspace
> >
> > Sean
> >
> > --
> > All messages to this mailing list should adhere to the Code of Conduct:
> > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> > <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/CA%2BxAuhMkoCiM%2BRJafRddPpH15wU%2BfB%3DJBwnAYA6m_OmogX9OhA%40mail.gmail.com
> > <
> https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhMkoCiM%2BRJafRddPpH15wU%2BfB%3DJBwnAYA6m_OmogX9OhA%40mail.gmail.com?utm_medium=email_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/cd567e6a-5b3d-23fd-a83c-a5bd32073dd7%40bibliothek.uni-kassel.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/CA%2BxAuhOnZJ5kcBYy4DS%2BM%3DyW1wqyaayBaCK5Q1kiajiGweq8Tg%40mail.gmail.com.

[dspace-tech] Duplicate key after restoring server from AIP backup

[Sean Carte]

I restored an entire site from an AIP backup, and now, when I attempt to
submit an item, I get this error:

Caused by: java.sql.BatchUpdateException: Batch entry 0 update
public.handle set resource_id='26a7cedb-76e7-4acc-a515-37708a3e1c7b'::uuid,
handle='123456789/9', resource_type_id=2 where handle_id=264 was aborted:
ERROR: duplicate key value violates unique constraint "handle_handle_key"
  Detail: Key (handle)=(123456789/9) already exists.  Call getNextException
to see other errors in the batch.

I think this is because I haven't run the update-sequences.sql that the
documentation suggests I should, but I can't find that script; there isn't
even a /dspace/etc/ directory:

ls /dspace/
assetstore  exportslog   solr upload
bin handle-server  reports   temp var
config  libsitemaps  triplestore  webapps

This is the documentation I've been using:

https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore#AIPBackupandRestore-RestoringEntireSite

DSpace version:  7.3-SNAPSHOT
  SCM revision:  e5f316c9adf78e59d8277a271a0fc2a2d21da0f8
SCM branch:  main
OS:  Linux(amd64) version 5.4.0-120-generic
  Applications:
 Discovery:  enabled.
   JRE:  Private Build version 11.0.15
   Ant version:  Apache Ant(TM) version 1.10.7 compiled on October 24 2019
 Maven version:  3.6.3
   DSpace home:  /dspace

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/CA%2BxAuhMkoCiM%2BRJafRddPpH15wU%2BfB%3DJBwnAYA6m_OmogX9OhA%40mail.gmail.com.

Re: [dspace-tech] Re: DSpace 7.2 behind a F5 internal firewall with wildcard certificate

[Sean Carte]

Thanks for the input, Mark. Unfortunately, I am not in a position to
suggest changes to the F5's configuration. Fortunately, Mohammad's
workaround worked.

Sean

On Fri, 8 Jul 2022 at 15:19, Mark H. Wood  wrote:

> On Fri, Jul 08, 2022 at 11:24:37AM +0200, Sean Carte wrote:
> > Ah, but wait, I remembered the chain of events that led to me installing
> > the cert, whose chain is broken:
> >
> > The F5 firewall seems to provide certification through its wildcard
> > certificate. So if you visit our current DSpace-CRIS 5 repository at
> > https://openscholar.dut.ac.za/  and check the connection security for
> that
> > site, you will see that it is verified by Sectigo Ltd. However, on that
> > server, I'm using a self-signed certificate. (It used to be LetsEncrypt
> > before the F5.)
> >
> > /etc/apache2/sites-enabled/default-ssl.conf
> > SSLCertificateFile
> /etc/ssl/certs/apache-selfsigned.crt
> > SSLCertificateKeyFile
> /etc/ssl/private/apache-selfsigned.key
> >
> > That didn't work for DSpace 7 (I forget the exact error, but I suspect it
> > was the verification error). So I requested the certificate from the IT
> > admin, and installed that.
> >
> > But it seems as though that doesn't even get seen by openssl s_client ...
> >
> > For comparison, if I run
> > openssl s_client -connect openscholar.dut.ac.za:443
> >
> > I get a similar error: Verification error: unable to verify the first
> > certificate.
> >
> > I'm really out of my depth here and not sure who or where to seek help.
> All
> > I know is that I can get this working unless it's behind the F5. But
> then,
> > in that case, I'm using LetsEncrypt.
>
> Your wildcard certificate for *.dut.ac.za is signed by "C = GB, ST =
> Greater Manchester, L = Salford, O = Sectigo Limited, CN = Sectigo RSA
> Organization Validation Secure Server CA" but that cert. is not in your
> client's trust store.  It's not in the trusted certificates bundle on
> my workstation, either.  Google has a lot of hits on "sectigo root
> certificate not trusted" which may shed some light.  You may need help
> from Sectigo customer support.  Or there may be some reason why that
> particular cert. is no longer trusted.
>
> Or it may be an intermediate authority whose cert. should be sent out
> with the server cert. to complete the trust chain to the root.  In
> that case, you may need to get a copy of that cert. and install it in
> the F5's trust store (once you're sure that *you* trust it).
>
> A client must be able to construct a path from the certificate
> presented by the site, through that cert.'s issuer cert. ("i:" in the
> certificate chain) via *its* issuer, etc. until it reaches a root
> certificate that it already trusts.
>
> --
> 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 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/Ysguzgx1FU%2BATiUl%40IUPUI.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/CA%2BxAuhN%3D3G8K2uVYUODc2zoryqjWUnef7CH%3DSLgYLS4nScww%2Bw%40mail.gmail.com.

Re: [dspace-tech] Re: DSpace 7.2 behind a F5 internal firewall with wildcard certificate

[Sean Carte]

Sorry, Michael, if I understood it myself, I might be able to explain it
better.

But thanks for your help in resolving this.

Sean

On Fri, 8 Jul 2022 at 16:33, Michael Plate 
wrote:

> Hi Sean,
>
> Am 08.07.22 um 11:24 schrieb Sean Carte:
> > Ah, but wait, I remembered the chain of events that led to me installing
> > the cert, whose chain is broken:
> >
> > The F5 firewall seems to provide certification through its wildcard
> > certificate. So if you visit our current DSpace-CRIS 5 repository at
> > https://openscholar.dut.ac.za/ <https://openscholar.dut.ac.za/>  and
> > check the connection security for that site, you will see that it is
> > verified by Sectigo Ltd. However, on that server, I'm using a
> > self-signed certificate. (It used to be LetsEncrypt before the F5.)
> […]
>
> I'm not sure if I can follow you…we only have IP-based FWs, the
> encryption is done always on the host.
> You have a self-signed cert and the F5 decrypts inside - like a browser
> / proxy- and encrypts again with another cert to outside ?
>
> Michael
>
> --
> 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/550e7ada-9d67-00bd-8eb7-0b24fb0dc867%40bibliothek.uni-kassel.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/CA%2BxAuhM-TzzF9SNKFtOGD6yjVD14sumh2gaAo4piCawRENDFmQ%40mail.gmail.com.

Re: [dspace-tech] Re: DSpace 7.2 behind a F5 internal firewall with wildcard certificate

[Sean Carte]

Thank you, Mohammad! I added an entry to /etc/hosts and it does appear to
work.

(I also tried your /etc/environment suggestion, but still got the 'unable
to verify the first certificate' error.)

Thanks again, I really appreciate your help.

Sean

On Sat, 9 Jul 2022 at 06:06, Mohammad S. AlMutairi  wrote:

> If your apache SSL configuration is correct you can force the NodeJS and
> the starting of the service later to access crdb.dut.ac.za directly using
> the server local IP instead of going thru the Public-IP/F5. You can do it
> by adding an entry into /etc/hosts for the server private IP address. The
> other way of overcoming this issue is by skipping the /etc/hosts file entry
> and doing the steps you see below:
>
> A) echo "export NODE_EXTRA_CA_CERTS=/etc/certs/crdb.dut.ac.za/cert.pem"
> >> /etc/environment
> B) source /etc/environment
> C) yarn test:rest
>
> Good luck
> On Friday, July 8, 2022 at 12:24:41 PM UTC+3 sean@gmail.com wrote:
>
>> Ah, but wait, I remembered the chain of events that led to me installing
>> the cert, whose chain is broken:
>>
>> The F5 firewall seems to provide certification through its wildcard
>> certificate. So if you visit our current DSpace-CRIS 5 repository at
>> https://openscholar.dut.ac.za/  and check the connection security for
>> that site, you will see that it is verified by Sectigo Ltd. However, on
>> that server, I'm using a self-signed certificate. (It used to be
>> LetsEncrypt before the F5.)
>>
>> /etc/apache2/sites-enabled/default-ssl.conf
>> SSLCertificateFile
>>  /etc/ssl/certs/apache-selfsigned.crt
>> SSLCertificateKeyFile
>> /etc/ssl/private/apache-selfsigned.key
>>
>> That didn't work for DSpace 7 (I forget the exact error, but I suspect it
>> was the verification error). So I requested the certificate from the IT
>> admin, and installed that.
>>
>> But it seems as though that doesn't even get seen by openssl s_client ...
>>
>> For comparison, if I run
>> openssl s_client -connect openscholar.dut.ac.za:443
>>
>> I get a similar error: Verification error: unable to verify the first
>> certificate.
>>
>> I'm really out of my depth here and not sure who or where to seek help.
>> All I know is that I can get this working unless it's behind the F5. But
>> then, in that case, I'm using LetsEncrypt.
>>
>> Sean
>>
>> On Thu, 7 Jul 2022 at 16:11, Sean Carte  wrote:
>>
>>> Thanks, Michael. That's useful. I'll follow up with our IT department.
>>>
>>> Sean
>>>
>>> On Thu, 7 Jul 2022 at 10:23, Plate, Michael <
>>> pl...@bibliothek.uni-kassel.de> wrote:
>>>
>>>> Hi Sean,
>>>>
>>>> your certificate chain is broken:
>>>>
>>>> openssl s_client -connect crdb.dut.ac.za:443
>>>>
>>>> CONNECTED(0003)
>>>> depth=0 C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban,
>>>> street = Overport, street = 7 Ritson Road, O = Durban University of
>>>> Technology, OU = ITSS, CN = *.dut.ac.za
>>>> verify error:num=20:unable to get local issuer certificate
>>>> verify return:1
>>>> depth=0 C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban,
>>>> street = Overport, street = 7 Ritson Road, O = Durban University of
>>>> Technology, OU = ITSS, CN = *.dut.ac.za
>>>> verify error:num=21:unable to verify the first certificate
>>>> verify return:1
>>>> depth=0 C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban,
>>>> street = Overport, street = 7 Ritson Road, O = Durban University of
>>>> Technology, OU = ITSS, CN = *.dut.ac.za
>>>> verify return:1
>>>> ---
>>>> Certificate chain
>>>>  0 s:C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban, street
>>>> = Overport, street = 7 Ritson Road, O = Durban University of Technology, OU
>>>> = ITSS, CN = *.dut.ac.za
>>>>i:C = GB, ST = Greater Manchester, L = Salford, O = Sectigo Limited,
>>>> CN = Sectigo RSA Organization Validation Secure Server CA
>>>> ---
>>>> […]
>>>>
>>>> browsers accept this, other programs are more picky about chain order .
>>>> If you cant't get around it, try letsencrypt and install certbot (its
>>>> in debian packages, no need for snap)
>>>>
>>>>
>>>> Michael
>>>>
>>>> 
>>>> Von: dspac...@goo

Re: [dspace-tech] Re: DSpace 7.2 behind a F5 internal firewall with wildcard certificate

[Sean Carte]

Ah, but wait, I remembered the chain of events that led to me installing
the cert, whose chain is broken:

The F5 firewall seems to provide certification through its wildcard
certificate. So if you visit our current DSpace-CRIS 5 repository at
https://openscholar.dut.ac.za/  and check the connection security for that
site, you will see that it is verified by Sectigo Ltd. However, on that
server, I'm using a self-signed certificate. (It used to be LetsEncrypt
before the F5.)

/etc/apache2/sites-enabled/default-ssl.conf
SSLCertificateFile  /etc/ssl/certs/apache-selfsigned.crt
SSLCertificateKeyFile /etc/ssl/private/apache-selfsigned.key

That didn't work for DSpace 7 (I forget the exact error, but I suspect it
was the verification error). So I requested the certificate from the IT
admin, and installed that.

But it seems as though that doesn't even get seen by openssl s_client ...

For comparison, if I run
openssl s_client -connect openscholar.dut.ac.za:443

I get a similar error: Verification error: unable to verify the first
certificate.

I'm really out of my depth here and not sure who or where to seek help. All
I know is that I can get this working unless it's behind the F5. But then,
in that case, I'm using LetsEncrypt.

Sean

On Thu, 7 Jul 2022 at 16:11, Sean Carte  wrote:

> Thanks, Michael. That's useful. I'll follow up with our IT department.
>
> Sean
>
> On Thu, 7 Jul 2022 at 10:23, Plate, Michael <
> pl...@bibliothek.uni-kassel.de> wrote:
>
>> Hi Sean,
>>
>> your certificate chain is broken:
>>
>> openssl s_client -connect crdb.dut.ac.za:443
>>
>> CONNECTED(0003)
>> depth=0 C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban, street
>> = Overport, street = 7 Ritson Road, O = Durban University of Technology, OU
>> = ITSS, CN = *.dut.ac.za
>> verify error:num=20:unable to get local issuer certificate
>> verify return:1
>> depth=0 C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban, street
>> = Overport, street = 7 Ritson Road, O = Durban University of Technology, OU
>> = ITSS, CN = *.dut.ac.za
>> verify error:num=21:unable to verify the first certificate
>> verify return:1
>> depth=0 C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban, street
>> = Overport, street = 7 Ritson Road, O = Durban University of Technology, OU
>> = ITSS, CN = *.dut.ac.za
>> verify return:1
>> ---
>> Certificate chain
>>  0 s:C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban, street =
>> Overport, street = 7 Ritson Road, O = Durban University of Technology, OU =
>> ITSS, CN = *.dut.ac.za
>>i:C = GB, ST = Greater Manchester, L = Salford, O = Sectigo Limited,
>> CN = Sectigo RSA Organization Validation Secure Server CA
>> ---
>> […]
>>
>> browsers accept this, other programs are more picky about chain order .
>> If you cant't get around it, try letsencrypt and install certbot (its in
>> debian packages, no need for snap)
>>
>>
>> Michael
>>
>> 
>> Von: dspace-tech@googlegroups.com  im
>> Auftrag von Sean Carte 
>> Gesendet: Donnerstag, 7. Juli 2022 07:54
>> An: Thiago Henrique Carvalho da Costa
>> Cc: DSpace Technical Support
>> Betreff: Re: [dspace-tech] Re: DSpace 7.2 behind a F5 internal firewall
>> with wildcard certificate
>>
>> […]
>>
>> --
>> 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/d00aa2e38fde4d2b8d28b164d724ce99%40bibliothek.uni-kassel.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/CA%2BxAuhPm8wh6rBDKk9UQyzLGy%2Bf0tu_YXrUfTGMb%2B5Z8w_qoig%40mail.gmail.com.

Re: [dspace-tech] Re: DSpace 7.2 behind a F5 internal firewall with wildcard certificate

[Sean Carte]

Thanks, Michael. That's useful. I'll follow up with our IT department.

Sean

On Thu, 7 Jul 2022 at 10:23, Plate, Michael 
wrote:

> Hi Sean,
>
> your certificate chain is broken:
>
> openssl s_client -connect crdb.dut.ac.za:443
>
> CONNECTED(0003)
> depth=0 C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban, street
> = Overport, street = 7 Ritson Road, O = Durban University of Technology, OU
> = ITSS, CN = *.dut.ac.za
> verify error:num=20:unable to get local issuer certificate
> verify return:1
> depth=0 C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban, street
> = Overport, street = 7 Ritson Road, O = Durban University of Technology, OU
> = ITSS, CN = *.dut.ac.za
> verify error:num=21:unable to verify the first certificate
> verify return:1
> depth=0 C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban, street
> = Overport, street = 7 Ritson Road, O = Durban University of Technology, OU
> = ITSS, CN = *.dut.ac.za
> verify return:1
> ---
> Certificate chain
>  0 s:C = ZA, postalCode = 4001, ST = KwaZulu-Natal, L = Durban, street =
> Overport, street = 7 Ritson Road, O = Durban University of Technology, OU =
> ITSS, CN = *.dut.ac.za
>i:C = GB, ST = Greater Manchester, L = Salford, O = Sectigo Limited, CN
> = Sectigo RSA Organization Validation Secure Server CA
> ---
> […]
>
> browsers accept this, other programs are more picky about chain order .
> If you cant't get around it, try letsencrypt and install certbot (its in
> debian packages, no need for snap)
>
>
> Michael
>
> 
> Von: dspace-tech@googlegroups.com  im
> Auftrag von Sean Carte 
> Gesendet: Donnerstag, 7. Juli 2022 07:54
> An: Thiago Henrique Carvalho da Costa
> Cc: DSpace Technical Support
> Betreff: Re: [dspace-tech] Re: DSpace 7.2 behind a F5 internal firewall
> with wildcard certificate
>
> […]
>
> --
> 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/d00aa2e38fde4d2b8d28b164d724ce99%40bibliothek.uni-kassel.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/CA%2BxAuhNMDoTNq4X-L0_V4A6eRF2Zx6n7iZa7xw9C-ApUpgWj9g%40mail.gmail.com.

Re: [dspace-tech] Re: DSpace 7.2 behind a F5 internal firewall with wildcard certificate

[Sean Carte]

Hi Thiago

No, I'm still stuck with this problem.

Sean

On Wed, 6 Jul 2022 at 18:19, Thiago Henrique Carvalho da Costa <
thiago.inst...@gmail.com> wrote:

> I have the same problem, did anyone manage to solve it?
> Ícone "Verificada pela comunidade"
>
> Em terça-feira, 31 de maio de 2022 às 09:45:24 UTC-3, john...@gmail.com
> escreveu:
>
>> come in the dspace slack and maybe I can help you
>>
>> On Tuesday, May 31, 2022 at 6:48:53 AM UTC-4 sean@gmail.com wrote:
>>
>>> I'm starting to think that it might not be possible to do this, but I'm
>>> hoping someone will tell me how very wrong I am.
>>>
>>> I have a server that is in our institution's DC, which is behind an F5
>>> firewall and there is a wildcard Sectigo certificate installed.
>>>
>>> My dspace local.cfg has the following settings:
>>> dspace.server.url = https://crdb.dut.ac.za/server
>>> dspace.ui.url = https://crdb.dut.ac.za
>>>
>>> I requested a certificate and key from the administrator and have this
>>> in /etc/apache2/sites-enabled/ssl.conf
>>>
>>> SSLCertificateFile /etc/certs/crdb.dut.ac.za/cert.pem
>>> SSLCertificateKeyFile /etc/certs/crdb.dut.ac.za/privkey.pem
>>> SSLCertificateChainFile /etc/certs/crdb.dut.ac.za/chain.pem
>>> Include /etc/certs/options-ssl-apache.conf
>>>
>>> # Proxy all HTTPS requests to "/server" from Apache to Tomcat via
>>> AJP connector
>>> ProxyPass /server ajp://localhost:8009/server
>>> ProxyPassReverse /server ajp://localhost:8009/server
>>>
>>> # Proxy all HTTPS requests from Apache to PM2 on port 4000
>>> ProxyPass / http://localhost:4000/
>>> ProxyPassReverse / http://localhost:4000/
>>>
>>> config.prod.yml
>>> ui:
>>>   ssl: false
>>>   host: localhost
>>>   port: 4000
>>>   nameSpace: /
>>> rest:
>>>   ssl: true
>>>   host: crdb.dut.ac.za
>>>   port: 443
>>>   nameSpace: /server
>>>
>>> When I run yarn test:rest:
>>> ...Testing connection to REST API at https://crdb.dut.ac.za/server/api.
>>> ..
>>>
>>> ERROR connecting to REST API
>>> Error: unable to verify the first certificate
>>>
>>> As expected, if I run node ./dist/server/main.js, I get the dreaded 'No
>>> _links section' error:
>>>
>>> GET / 500 1356.467 ms - 231171
>>> No _links section found at https://crdb.dut.ac.za/server/api
>>>
>>> Am I wasting my time with this, or has anybody managed to get this
>>> working in a similar situation with a proxy firewall handing out a wildcard
>>> certificate?
>>>
>>> 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/33a6bd12-384e-477f-a165-6dedf18b3d98n%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/CA%2BxAuhMgqiiy%3DdmRhHG57bT%2BWDxMhJ75Bomin80s%3Dz%3DXwoj%2Bnw%40mail.gmail.com.

Re: [dspace-tech] Re: Solr Query of download and view.

[Sean Carte]

Hi Karol

If you're comfortable trawling through the solr.log, you'll find the
community uuid referenced when you access that community, e.g.:

2022-06-08 13:50:26,967 INFO  org.apache.solr.core.SolrCore @ [search]
webapp=/solr path=/select
params={f.has_content_in_original_bundle.facet.limit=3=author_filter=subject_tax_0_filter=has_content_in_original_bundle=handle,search.resourcetype,search.resourceid=0=NOT(withdrawn:true)=NOT(discoverable:false)=location:m
*333b0c4a-db89-422f-9d1d-3bbcb9a5d3ae*=read:(g186b0bff-3460-4266-b003-ddc0c4e08bb3+OR+g186b0bff-3460-4266-b003-ddc0c4e08bb3)_filter.facet.sort=count=0=2_tax_0_filter.facet.limit=11=dateIssued.year:[2010+TO+2020]=dateIssued.year:[2008+TO+2009]=*:*_tax_0_filter.facet.sort=count=1=true_content_in_original_bundle.facet.sort=count=javabin=0_filter.facet.limit=11}
hits=2640 status=0 QTime=1

Probably easier to query the database, though:

SELECT * FROM community;
 community_id | uuid | admin |
logo_bitstream_id
--+--+---+---
8 | 333b0c4a-db89-422f-9d1d-3bbcb9a5d3ae |   |
9 | 9558b065-ff99-48b8-b7a0-d8393700c5f1 |   |
   10 | 8921fc45-ab5c-4e44-9c49-927ecaa888eb |   |
   11 | 1899b53d-608a-4010-ba7a-88b22f217529 |   |
   12 | d5198570-ffe8-4977-ac2c-a88439c0d8ef |   |
   13 | 4f620c0e-ec85-48a5-b2e6-9bf6f6e9508c |   |
(6 rows)

I'm assuming you're using DSpace 6.

(I'm fairly certain there was some trick you could use to get the
community/collection id from the UI, but I can't remember how to do it.)

Sean


On Wed, 8 Jun 2022 at 11:55, Karol Sokalski  wrote:

> Hi,
>
> Can you please tell me how I can find the internal-id for Community?
> Thanks,
>
> Karol
>
> poniedziałek, 19 września 2016 o 17:13:34 UTC+2 Bruno Nocera Zanette
> napisał(a):
>
>> Hey! Glad it helped!!
>>
>> As a said, you will have to parse the response to get this info. The
>> field of interest for you is "numFound".
>>
>> For example, when i execute the query that i cited in the first message i
>> get the following response:
>>
>> {
>>   "responseHeader":{
>> "status":0,
>> "QTime":2,
>> "params":{
>>   "q":"type:2 AND (id:68056753-e460-4f80-a08a-f8febfbd07f7)",
>>   "indent":"true",
>>   "fq":"statistics_type:[* TO *] AND statistics_type:view",
>>   "wt":"json"}},
>>   "response":{"numFound":4,"start":0,"docs":[
>>   {
>> "ip":"127.0.0.1",
>> "referrer":"http://localhost:8080/xmlui/;,
>> "dns":"localhost.",
>> "userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:48.0) 
>> Gecko/20100101 Firefox/48.0",
>> "isBot":false,
>> "id":"68056753-e460-4f80-a08a-f8febfbd07f7",
>> "type":2,
>> "owningColl":["88c16bca-e689-4a71-b8f3-112191758c9a"],
>> "owningComm":["bc362b91-eb6d-4c95-bf2c-77dc2aeb20d4"],
>> "time":"2016-09-18T13:16:47.936Z",
>> "epersonid":"041c27dd-7c00-49c4-9192-55a3aed42994",
>> "statistics_type":"view",
>> "uid":"6d845ff5-2a9d-441f-a081-8190485f231c",
>> "_version_":1545826895597142016},
>>   {...}
>> }
>>
>> In the beggining of the response there are the params that were used. Then 
>> it comes the important part, that is the response itself. As any other 
>> query, it says how many results were found and then the results itself. So, 
>> if you are looking for some kind of statistic, the result will be how many 
>> statistics were found.
>>
>> How you will do it depends on the language you are using, but almost 
>> definitely will be something like this (written on Ruby):
>> parsedResponse = JSON.parse(response)  # Parse the result
>> numFounds = parsedResponse["response"]["numFound"] # Access the response 
>> field and then the attribute numFound.
>>
>> And then you can iterate through the results if you want:
>> parsed_response["response"]["docs"].each do |r|
>>  puts r["ip"]
>> end
>>
>> If the number of found results isn't the same as it appears on the xmlui 
>> interface you have to revise the query, because it should be.
>>
>>
>> Em seg, 19 de set de 2016 às 08:59, Faiyaz Ahmed 
>> escreveu:
>>
>>> Thank you so much Bruno for response and now I understand to run Solr
>>> Query.
>>>
>>> Below query I got from solr.log file :
>>>
>>> 2016-09-19 15:57:44,851 INFO  org.apache.solr.core.SolrCore @
>>> [statistics] webapp=/solr path=/select
>>> params={facet=true=localhost:8080/solr/statistics-2015,localhost:8080/solr/statistics=1=type:+2+AND++id:64=10=id=javabin=-isBot:true=-(bundleName:[*+TO+*]-bundleName:ORIGINAL)=-(statistics_type:[*+TO+*]+AND+-statistics_type:view)=2=0}
>>> hits=23 status=0 QTime=4
>>>
>>> *I run *:
>>> facet=true=localhost:8080/solr/statistics-2015,localhost:8080/solr/statistics=1=type:+2+AND++id:64=10=id=javabin=-isBot:true=-(bundleName:[*+TO+*]-bundleName:ORIGINAL)=-(statistics_type:[*+TO+*]+AND+-statistics_type:view)=2=0

[dspace-tech] DSpace 7.2 behind a F5 internal firewall with wildcard certificate

[Sean Carte]

I'm starting to think that it might not be possible to do this, but I'm
hoping someone will tell me how very wrong I am.

I have a server that is in our institution's DC, which is behind an F5
firewall and there is a wildcard Sectigo certificate installed.

My dspace local.cfg has the following settings:
dspace.server.url = https://crdb.dut.ac.za/server
dspace.ui.url = https://crdb.dut.ac.za

I requested a certificate and key from the administrator and have this in
/etc/apache2/sites-enabled/ssl.conf

SSLCertificateFile /etc/certs/crdb.dut.ac.za/cert.pem
SSLCertificateKeyFile /etc/certs/crdb.dut.ac.za/privkey.pem
SSLCertificateChainFile /etc/certs/crdb.dut.ac.za/chain.pem
Include /etc/certs/options-ssl-apache.conf

# Proxy all HTTPS requests to "/server" from Apache to Tomcat via AJP
connector
ProxyPass /server ajp://localhost:8009/server
ProxyPassReverse /server ajp://localhost:8009/server

# Proxy all HTTPS requests from Apache to PM2 on port 4000
ProxyPass / http://localhost:4000/
ProxyPassReverse / http://localhost:4000/

config.prod.yml
ui:
  ssl: false
  host: localhost
  port: 4000
  nameSpace: /
rest:
  ssl: true
  host: crdb.dut.ac.za
  port: 443
  nameSpace: /server

When I run yarn test:rest:
...Testing connection to REST API at https://crdb.dut.ac.za/server/api...

ERROR connecting to REST API
Error: unable to verify the first certificate

As expected, if I run node ./dist/server/main.js, I get the dreaded 'No
_links section' error:

GET / 500 1356.467 ms - 231171
No _links section found at https://crdb.dut.ac.za/server/api

Am I wasting my time with this, or has anybody managed to get this working
in a similar situation with a proxy firewall handing out a wildcard
certificate?

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/CA%2BxAuhPKzTDUvHgCM2PqOYGBNfc0Aw4dMKFonLOmb%2BT3zcjd9g%40mail.gmail.com.

Re: [dspace-tech] Database space used

[Sean Carte]

Hi Sarah

If you also need the size of the assetstore directory, this should do it:

du -sh /assetstore/

But check your dspace.cfg that that is the correct directory.

Sean

On Wed, 23 Mar 2022 at 13:55, Mark H. Wood  wrote:

> On Tue, Mar 22, 2022 at 08:05:13AM -0400, Sarah Butash wrote:
> > I've been asked to report the amount of space used for our DSpace data.
> I
> > can report the size of the volume allocated for the database, but this
> > doesn't give me the actual data used space.  We are on DSpace 5.10 on a
> > linux server.
>
>
> https://makandracards.com/makandra/37935-postgresql-show-size-of-all-databases
>
> gives a query that will show you the sizes of *all* databases in the
> cluster.  It shouldn't be too hard to alter it to select just the
> database you want, and to report in other units.
>
> --
> 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 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/YjsKsHViqcr3VYaG%40IUPUI.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/CA%2BxAuhPHnkvV00H-29XZ8_HASWn29y2rWivLWN9pM%2BN5YOeSgQ%40mail.gmail.com.

[dspace-tech] Re: DSpace-CRIS: error viewing researcherDetailsPage

[Sean Carte]

Also, I have rebuilt the discovery index with:

/bin/dspace index-discovery -fb

Sean

On Tue, 1 Mar 2022 at 16:49, Sean Carte  wrote:

> I am trying to restore a backup of a functional DSpace-CRIS 5.10 server
> and I have everything working except the researcher pages. (They work on
> the original server.)
>
> When I visit a researcher profile such as, /cris/rp/rp02961, the following
> error is generated:
>
> 2022-03-01 14:34:29,573 WARN
>  org.dspace.app.webui.servlet.InternalErrorServlet @
> :session_id=3F089C61FAA2443E4713DE811CD0B48C:internal_error:-- URL Was:
> http://10.4.36.37:8080/dspace-cris/researcherDetailsPage.jsp
> -- Method: GET
> -- Parameters were:
>
> javax.servlet.ServletException: org.apache.jasper.JasperException:
> javax.servlet.ServletException: org.apache.jasper.JasperException:
> /dspace-cris/commonDetailsPage.jsp (line: [60], column: [8])
> [${entity.class.simpleName}.tab.${area.shortName}.label] contains invalid
> expression(s): [javax.el.ELException: Failed to parse the expression
> [${entity.class.simpleName}.tab.${area.shortName}.label]]
> at
> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:85)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:710)
> at
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:457)
> at
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:384)
> at
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
> at
> org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:238)
> at
> org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:264)
> at
> org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1216)
> at
> org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1001)
> at
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:945)
> at
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:867)
> at
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:951)
> at
> org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:842)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:626)
> at
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:827)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
> at
> org.dspace.app.webui.cris.filter.DSpaceContextCleanupFilter.doFilter(DSpaceContextCleanupFilter.java:54)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
> at
> org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:106)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
> at
> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:542)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo

[dspace-tech] DSpace-CRIS: error viewing researcherDetailsPage

[Sean Carte]

I am trying to restore a backup of a functional DSpace-CRIS 5.10 server and
I have everything working except the researcher pages. (They work on the
original server.)

When I visit a researcher profile such as, /cris/rp/rp02961, the following
error is generated:

2022-03-01 14:34:29,573 WARN
 org.dspace.app.webui.servlet.InternalErrorServlet @
:session_id=3F089C61FAA2443E4713DE811CD0B48C:internal_error:-- URL Was:
http://10.4.36.37:8080/dspace-cris/researcherDetailsPage.jsp
-- Method: GET
-- Parameters were:

javax.servlet.ServletException: org.apache.jasper.JasperException:
javax.servlet.ServletException: org.apache.jasper.JasperException:
/dspace-cris/commonDetailsPage.jsp (line: [60], column: [8])
[${entity.class.simpleName}.tab.${area.shortName}.label] contains invalid
expression(s): [javax.el.ELException: Failed to parse the expression
[${entity.class.simpleName}.tab.${area.shortName}.label]]
at
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:85)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:710)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:457)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:384)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
at
org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:238)
at
org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:264)
at
org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1216)
at
org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1001)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:945)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:867)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:951)
at
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:626)
at
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:827)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at
org.dspace.app.webui.cris.filter.DSpaceContextCleanupFilter.doFilter(DSpaceContextCleanupFilter.java:54)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:106)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:542)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:346)
at
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:374)
at
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:887)
at

Re: [dspace-tech] Re: Restoring a deleted collection

[Sean Carte]

Thanks again, Tim. Everything worked perfectly thanks to your assistance.

Sean

On Tue, 22 Feb 2022 at 20:43, Sean Carte  wrote:

> That worked beautifully; thanks, Tim!
>
> I'll tackle the restoring part tomorrow.
>
> Sean
>
> On Tue, 22 Feb 2022 at 17:41, Tim Donohue  wrote:
>
>> Hi Sean,
>>
>> Based on that error, it appears it cannot find your system's "temp"
>> directory, which is needed to built the AIPs. Usually, a Java install has a
>> default "java.io.tmpdir" which will be used.
>>
>> But, you can also override it by setting "upload.temp.dir" in your
>> dspace.cfg/local.cfg.  So, if you make sure "upload.temp.dir" points to a
>> valid temp location (used to build/process AIPs) then that should hopefully
>> get you past that error.
>>
>> Tim
>> --
>> *From:* Sean Carte 
>> *Sent:* Tuesday, February 22, 2022 1:40 AM
>> *To:* Tim Donohue 
>> *Cc:* DSpace Technical Support 
>> *Subject:* Re: [dspace-tech] Re: Restoring a deleted collection
>>
>> Hi Tim
>>
>> I went with the third option and have spun up a test instance from a
>> backup before the collection was deleted, but I can't get the AIP packager
>> to work recursively on the collection; I get: exception; no such file or
>> directory.
>>
>> If I try a single item from that collection it works:
>>
>>  /dspace/bin/dspace packager -d -a -t AIP -e sean.ca...@gmail.com -i
>> 10413/20198 20198.zip
>>
>> Disseminating DSpace ITEM [ hdl=10413/20198 ] to 20198.zip
>>
>> Also disseminating all child objects (recursive mode)..
>> This may take a while, please check your logs for ongoing status while we
>> process each package.
>>
>> CREATED a total of 1 dissemination package files.
>>
>> Would you like to view a list of all files that were created? [y/n]: y
>>
>>
>>
>> CREATED package file: /dspace/20198.zip
>>
>>
>> But not for the collection:
>>
>> /dspace/bin/dspace packager -d -a -t AIP -e sean.ca...@gmail.com -i
>> 10413/6680 6680.zip
>>
>> Disseminating DSpace COLLECTION [ hdl=10413/6680 ] to 6680.zip
>>
>> Also disseminating all child objects (recursive mode)..
>> This may take a while, please check your logs for ongoing status while we
>> process each package.
>> Exception: No such file or directory
>> java.io.IOException: No such file or directory
>> at java.io.UnixFileSystem.createFileExclusively(Native Method)
>> at java.io.File.createTempFile(File.java:2063)
>> at
>> org.dspace.content.crosswalk.RoleCrosswalk.disseminateElement(RoleCrosswalk.java:190)
>> at
>> org.dspace.content.packager.AbstractMETSDisseminator.crosswalkToMetsElement(AbstractMETSDisseminator.java:1356)
>> at
>> org.dspace.content.packager.AbstractMETSDisseminator.makeMdSec(AbstractMETSDisseminator.java:626)
>> at
>> org.dspace.content.packager.AbstractMETSDisseminator.addToAmdSec(AbstractMETSDisseminator.java:739)
>> at
>> org.dspace.content.packager.AbstractMETSDisseminator.addAmdSec(AbstractMETSDisseminator.java:765)
>> at
>> org.dspace.content.packager.AbstractMETSDisseminator.makeManifest(AbstractMETSDisseminator.java:862)
>> at
>> org.dspace.content.packager.AbstractMETSDisseminator.writeZipPackage(AbstractMETSDisseminator.java:334)
>> at
>> org.dspace.content.packager.AbstractMETSDisseminator.disseminate(AbstractMETSDisseminator.java:271)
>> at
>> org.dspace.content.packager.DSpaceAIPDisseminator.disseminate(DSpaceAIPDisseminator.java:165)
>> at
>> org.dspace.content.packager.AbstractPackageDisseminator.disseminateAll(AbstractPackageDisseminator.java:102)
>> at org.dspace.app.packager.Packager.disseminate(Packager.java:642)
>> at org.dspace.app.packager.Packager.main(Packager.java:461)
>> 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)
>>
>>
>> I have tried other collection handles with the same result. And a
>> sitewide export also fails with the same error.
>>
>> Any ideas where I've gone wrong?
>>
>> Sean
>>
>> On Tue, 15 Feb 2022 at 17:40, 'Tim Donohue' via DSpace Technical S

Re: [dspace-tech] Re: Restoring a deleted collection

[Sean Carte]

That worked beautifully; thanks, Tim!

I'll tackle the restoring part tomorrow.

Sean

On Tue, 22 Feb 2022 at 17:41, Tim Donohue  wrote:

> Hi Sean,
>
> Based on that error, it appears it cannot find your system's "temp"
> directory, which is needed to built the AIPs. Usually, a Java install has a
> default "java.io.tmpdir" which will be used.
>
> But, you can also override it by setting "upload.temp.dir" in your
> dspace.cfg/local.cfg.  So, if you make sure "upload.temp.dir" points to a
> valid temp location (used to build/process AIPs) then that should hopefully
> get you past that error.
>
> Tim
> --
> *From:* Sean Carte 
> *Sent:* Tuesday, February 22, 2022 1:40 AM
> *To:* Tim Donohue 
> *Cc:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] Re: Restoring a deleted collection
>
> Hi Tim
>
> I went with the third option and have spun up a test instance from a
> backup before the collection was deleted, but I can't get the AIP packager
> to work recursively on the collection; I get: exception; no such file or
> directory.
>
> If I try a single item from that collection it works:
>
>  /dspace/bin/dspace packager -d -a -t AIP -e sean.ca...@gmail.com -i
> 10413/20198 20198.zip
>
> Disseminating DSpace ITEM [ hdl=10413/20198 ] to 20198.zip
>
> Also disseminating all child objects (recursive mode)..
> This may take a while, please check your logs for ongoing status while we
> process each package.
>
> CREATED a total of 1 dissemination package files.
>
> Would you like to view a list of all files that were created? [y/n]: y
>
>
>
> CREATED package file: /dspace/20198.zip
>
>
> But not for the collection:
>
> /dspace/bin/dspace packager -d -a -t AIP -e sean.ca...@gmail.com -i
> 10413/6680 6680.zip
>
> Disseminating DSpace COLLECTION [ hdl=10413/6680 ] to 6680.zip
>
> Also disseminating all child objects (recursive mode)..
> This may take a while, please check your logs for ongoing status while we
> process each package.
> Exception: No such file or directory
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.createTempFile(File.java:2063)
> at
> org.dspace.content.crosswalk.RoleCrosswalk.disseminateElement(RoleCrosswalk.java:190)
> at
> org.dspace.content.packager.AbstractMETSDisseminator.crosswalkToMetsElement(AbstractMETSDisseminator.java:1356)
> at
> org.dspace.content.packager.AbstractMETSDisseminator.makeMdSec(AbstractMETSDisseminator.java:626)
> at
> org.dspace.content.packager.AbstractMETSDisseminator.addToAmdSec(AbstractMETSDisseminator.java:739)
> at
> org.dspace.content.packager.AbstractMETSDisseminator.addAmdSec(AbstractMETSDisseminator.java:765)
> at
> org.dspace.content.packager.AbstractMETSDisseminator.makeManifest(AbstractMETSDisseminator.java:862)
> at
> org.dspace.content.packager.AbstractMETSDisseminator.writeZipPackage(AbstractMETSDisseminator.java:334)
> at
> org.dspace.content.packager.AbstractMETSDisseminator.disseminate(AbstractMETSDisseminator.java:271)
> at
> org.dspace.content.packager.DSpaceAIPDisseminator.disseminate(DSpaceAIPDisseminator.java:165)
> at
> org.dspace.content.packager.AbstractPackageDisseminator.disseminateAll(AbstractPackageDisseminator.java:102)
> at org.dspace.app.packager.Packager.disseminate(Packager.java:642)
> at org.dspace.app.packager.Packager.main(Packager.java:461)
> 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)
>
>
> I have tried other collection handles with the same result. And a sitewide
> export also fails with the same error.
>
> Any ideas where I've gone wrong?
>
> Sean
>
> On Tue, 15 Feb 2022 at 17:40, 'Tim Donohue' via DSpace Technical Support <
> dspace-tech@googlegroups.com> wrote:
>
> Hi Sean,
>
> Unfortunately, it's not at all easy to restore a single Collection from a
> database backup.  But, here's a few other options to consider:
>
> If you happened to also do a recent AIP backup, then that's much easier,
> as you can just restore the Collection by reimporting its AIP(s) in restore
> mode:
> https://wiki.lyrasis.org/display/DSDOC6x/AIP+Backup+and+Restore#AIPBackupandRestore-Restoring/ReplacingusingAIP(s)
>
> Another option would be to see if y

Re: [dspace-tech] Re: Restoring a deleted collection

[Sean Carte]

Hi Tim

I went with the third option and have spun up a test instance from a backup
before the collection was deleted, but I can't get the AIP packager to work
recursively on the collection; I get: exception; no such file or directory.

If I try a single item from that collection it works:

 /dspace/bin/dspace packager -d -a -t AIP -e sean.ca...@gmail.com -i
10413/20198 20198.zip

Disseminating DSpace ITEM [ hdl=10413/20198 ] to 20198.zip

Also disseminating all child objects (recursive mode)..
This may take a while, please check your logs for ongoing status while we
process each package.

CREATED a total of 1 dissemination package files.

Would you like to view a list of all files that were created? [y/n]: y



CREATED package file: /dspace/20198.zip


But not for the collection:

/dspace/bin/dspace packager -d -a -t AIP -e sean.ca...@gmail.com -i
10413/6680 6680.zip

Disseminating DSpace COLLECTION [ hdl=10413/6680 ] to 6680.zip

Also disseminating all child objects (recursive mode)..
This may take a while, please check your logs for ongoing status while we
process each package.
Exception: No such file or directory
java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createTempFile(File.java:2063)
at
org.dspace.content.crosswalk.RoleCrosswalk.disseminateElement(RoleCrosswalk.java:190)
at
org.dspace.content.packager.AbstractMETSDisseminator.crosswalkToMetsElement(AbstractMETSDisseminator.java:1356)
at
org.dspace.content.packager.AbstractMETSDisseminator.makeMdSec(AbstractMETSDisseminator.java:626)
at
org.dspace.content.packager.AbstractMETSDisseminator.addToAmdSec(AbstractMETSDisseminator.java:739)
at
org.dspace.content.packager.AbstractMETSDisseminator.addAmdSec(AbstractMETSDisseminator.java:765)
at
org.dspace.content.packager.AbstractMETSDisseminator.makeManifest(AbstractMETSDisseminator.java:862)
at
org.dspace.content.packager.AbstractMETSDisseminator.writeZipPackage(AbstractMETSDisseminator.java:334)
at
org.dspace.content.packager.AbstractMETSDisseminator.disseminate(AbstractMETSDisseminator.java:271)
at
org.dspace.content.packager.DSpaceAIPDisseminator.disseminate(DSpaceAIPDisseminator.java:165)
at
org.dspace.content.packager.AbstractPackageDisseminator.disseminateAll(AbstractPackageDisseminator.java:102)
at org.dspace.app.packager.Packager.disseminate(Packager.java:642)
at org.dspace.app.packager.Packager.main(Packager.java:461)
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)


I have tried other collection handles with the same result. And a sitewide
export also fails with the same error.

Any ideas where I've gone wrong?

Sean

On Tue, 15 Feb 2022 at 17:40, 'Tim Donohue' via DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> Hi Sean,
>
> Unfortunately, it's not at all easy to restore a single Collection from a
> database backup.  But, here's a few other options to consider:
>
> If you happened to also do a recent AIP backup, then that's much easier,
> as you can just restore the Collection by reimporting its AIP(s) in restore
> mode:
> https://wiki.lyrasis.org/display/DSDOC6x/AIP+Backup+and+Restore#AIPBackupandRestore-Restoring/ReplacingusingAIP(s)
>
> Another option would be to see if you can just restore the entire database
> from that backup (which can result in data loss if you've added new data
> since that last backup occurred). If you restore the database though, you'd
> also likely need to restore the "[dspace]/assetstore" folder from a backup
> at the same time (as any Item's files that were deleted from that
> assetstore folder during the Collection deletion would also require
> restoring).
>
> A third option, if you have a backup of the database & assetstore folder
> from around the same time would be to use those to spin up a separate
> *test* instance of your DSpace site, with the same data as that last
> backup.  Then you could do an AIP backup of the deleted Collection at that
> point in time, and use the AIP tools to then restore it into your
> production DSpace  (make sure to fully test the restoration though before
> running it against your production site)
>
> My recommendation would be to go with one of those approaches, when
> possible.  Restoring a single collection from a database backup would be
> highly complex to do at the database levelas it essentially would
> require somehow restoring the necessary deleted columns to several tables
> at once.  It's something even I've never done before.
>
> Good luck,
>
> Tim
>
>
>
> On Tuesday, February 15, 2022 at 4:35:54 AM UTC-6 sean@gmail.com
> wrote:
>

Re: [dspace-tech] Re: Restoring a deleted collection

[Sean Carte]

Thanks, Tim. That's very helpful.

Sean

On Tue, 15 Feb 2022 at 17:40, 'Tim Donohue' via DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> Hi Sean,
>
> Unfortunately, it's not at all easy to restore a single Collection from a
> database backup.  But, here's a few other options to consider:
>
> If you happened to also do a recent AIP backup, then that's much easier,
> as you can just restore the Collection by reimporting its AIP(s) in restore
> mode:
> https://wiki.lyrasis.org/display/DSDOC6x/AIP+Backup+and+Restore#AIPBackupandRestore-Restoring/ReplacingusingAIP(s)
>
> Another option would be to see if you can just restore the entire database
> from that backup (which can result in data loss if you've added new data
> since that last backup occurred). If you restore the database though, you'd
> also likely need to restore the "[dspace]/assetstore" folder from a backup
> at the same time (as any Item's files that were deleted from that
> assetstore folder during the Collection deletion would also require
> restoring).
>
> A third option, if you have a backup of the database & assetstore folder
> from around the same time would be to use those to spin up a separate
> *test* instance of your DSpace site, with the same data as that last
> backup.  Then you could do an AIP backup of the deleted Collection at that
> point in time, and use the AIP tools to then restore it into your
> production DSpace  (make sure to fully test the restoration though before
> running it against your production site)
>
> My recommendation would be to go with one of those approaches, when
> possible.  Restoring a single collection from a database backup would be
> highly complex to do at the database levelas it essentially would
> require somehow restoring the necessary deleted columns to several tables
> at once.  It's something even I've never done before.
>
> Good luck,
>
> Tim
>
>
>
> On Tuesday, February 15, 2022 at 4:35:54 AM UTC-6 sean@gmail.com
> wrote:
>
>> Is it possible to restore a deleted collection? This is on DSpace 6. We
>> do have backups of the database.
>>
>> 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/57e9c19f-f341-4990-a9da-2ad20f87cc31n%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/CA%2BxAuhO7J2RWT13A%2BPDJsJjNBYyCMbGRmUVHmFg8W%2BB-Z-PYfA%40mail.gmail.com.

[dspace-tech] Restoring a deleted collection

[Sean Carte]

Is it possible to restore a deleted collection? This is on DSpace 6. We do
have backups of the database.

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/CA%2BxAuhMXEFmX9NX94PK2E53drp3HbSvRJKbpt4G7WrRDV_Y%3DQA%40mail.gmail.com.

Re: [dspace-tech] what type SSL certificate should I obtain?

[Sean Carte]

Letsencrypt is free and well-supported.

letsencrypt.org

On Sat, 12 Feb 2022, 05:50 Phillip jan,  wrote:

> Are there any specific SSL certificate I should buy? Can yo guys recommend
> an SSL certificate provider that is cheap? 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/a38ad021-251d-4a4e-bb65-8cd4dbc74aden%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/CA%2BxAuhO1iRzb-Jfz3gLi0zrxPsYJo76dAqHE5yPxbFs1aqHExw%40mail.gmail.com.

Re: [dspace-tech] Re: IIIF configuration for DSpace 7

[Sean Carte]

Thanks, Tim, for your assistance.

The colon between 'run' and 'start' was just a typo; sorry.

Yarn version is 1.22.17.

Yes, I have the Angular UI running.

And, finally, yes, "yarn run clean" followed by a "yarn install" did
resolve the issue.

Thanks again!

Sean

On Wed, 26 Jan 2022 at 17:21, 'Tim Donohue' via DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> Hi Sean,
>
> You shouldn't need to install anything manually at all... the `yarn run`
> command should install whatever you need automatically.
>
> It looks like you have a typo in your yarn command... there's a colon (:)
> between "run" and "start" which is not valid.  It's possible that's just a
> typo in your email, but the correct command is "yarn run
> start:mirador:prod".
>
> What version of Yarn are you using (we only support v1.x at this time)?
> Have you already successfully gotten the DSpace Angular UI running on your
> machine (I'd recommend getting it running first, just to be sure that
> there's not some other issue unrelated to IIIF that you may be hitting).
>
> I'm not sure if any of that will help, but it almost sounds like something
> else is wrong with your setup that is unrelated to IIIF.  You could also
> try to remove & reinstall all third-party libraries by doing a "yarn run
> clean" followed by a "yarn install", and then try again to see if Mirador
> can build properly.
>
> Tim
>
> On Wednesday, January 26, 2022 at 5:29:12 AM UTC-6 sean@gmail.com
> wrote:
>
>> I've been following the instructions at:
>> https://wiki.lyrasis.org/display/DSDOC7x/IIIF+Configuration to get IIIF
>> support working, but have not been able to enable the Mirador viewer.
>>
>> When I run `yarn run:start:mirador:prod`, I get many errors like:
>> ERROR in ./node_modules/mirador/dist/es/src/components/FullScreenButton.js
>> Module not found: Error: Can't resolve
>> '@material-ui/icons/FullscreenExitSharp' in
>> '/home/seanc/dspace-angular-dspace-7.1/node_modules/mirador/dist/es/src/components'
>>  @ ./node_modules/mirador/dist/es/src/components/FullScreenButton.js
>> 23:0-72 58:64-82
>>  @ ./node_modules/mirador/dist/es/src/containers/FullScreenButton.js
>>  @
>> ./node_modules/mirador/dist/es/src/components/WorkspaceControlPanelButtons.js
>>  @
>> ./node_modules/mirador/dist/es/src/containers/WorkspaceControlPanelButtons.js
>>  @ ./node_modules/mirador/dist/es/src/components/WorkspaceControlPanel.js
>>  @ ./node_modules/mirador/dist/es/src/containers/WorkspaceControlPanel.js
>>  @ ./node_modules/mirador/dist/es/src/components/WorkspaceArea.js
>>  @ ./node_modules/mirador/dist/es/src/containers/WorkspaceArea.js
>>  @ ./node_modules/mirador/dist/es/src/components/App.js
>>  @ ./node_modules/mirador/dist/es/src/lib/MiradorViewer.js
>>  @ ./node_modules/mirador/dist/es/src/init.js
>>  @ ./node_modules/mirador/dist/es/src/index.js
>>  @ ./src/mirador-viewer/index.js
>>
>> I installed material-ui with `npm install @mui/material`, and it seemed
>> to install successfully, but the errors continue.
>>
>> I was seeing warnings about blueprintsjs not being found, so I installed
>> it with `npm install --save @blueprintjs/core`, and the warnings are now
>> gone.
>>
>> Am I installing the correct module for @material-ui?
>>
>> Sean
>>
>> DSpace version:  7.2-SNAPSHOT
>>   SCM revision:  fcc9f045a2f724db0bfa47b383c97050ea1943c2
>> SCM branch:  main
>> OS:  Linux(amd64) version 5.4.0-94-generic
>>   Applications:
>>  Discovery:  enabled.
>>JRE:  Ubuntu version 11.0.13
>>Ant version:  Apache Ant(TM) version 1.10.7 compiled on October 24 2019
>>  Maven version:  3.6.3
>>
>>
>>
>> --
> 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/03811773-f726-4f33-83e7-be0bb69905a1n%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/CA%2BxAuhM2iKgWOC02jSKBLPPygZsYJGGGfa1q-3m9qz7d36f3xQ%40mail.gmail.com.

[dspace-tech] IIIF configuration for DSpace 7

[Sean Carte]

I've been following the instructions at:
https://wiki.lyrasis.org/display/DSDOC7x/IIIF+Configuration to get IIIF
support working, but have not been able to enable the Mirador viewer.

When I run `yarn run:start:mirador:prod`, I get many errors like:
ERROR in ./node_modules/mirador/dist/es/src/components/FullScreenButton.js
Module not found: Error: Can't resolve
'@material-ui/icons/FullscreenExitSharp' in
'/home/seanc/dspace-angular-dspace-7.1/node_modules/mirador/dist/es/src/components'
 @ ./node_modules/mirador/dist/es/src/components/FullScreenButton.js
23:0-72 58:64-82
 @ ./node_modules/mirador/dist/es/src/containers/FullScreenButton.js
 @
./node_modules/mirador/dist/es/src/components/WorkspaceControlPanelButtons.js
 @
./node_modules/mirador/dist/es/src/containers/WorkspaceControlPanelButtons.js
 @ ./node_modules/mirador/dist/es/src/components/WorkspaceControlPanel.js
 @ ./node_modules/mirador/dist/es/src/containers/WorkspaceControlPanel.js
 @ ./node_modules/mirador/dist/es/src/components/WorkspaceArea.js
 @ ./node_modules/mirador/dist/es/src/containers/WorkspaceArea.js
 @ ./node_modules/mirador/dist/es/src/components/App.js
 @ ./node_modules/mirador/dist/es/src/lib/MiradorViewer.js
 @ ./node_modules/mirador/dist/es/src/init.js
 @ ./node_modules/mirador/dist/es/src/index.js
 @ ./src/mirador-viewer/index.js

I installed material-ui with `npm install @mui/material`, and it seemed to
install successfully, but the errors continue.

I was seeing warnings about blueprintsjs not being found, so I installed it
with `npm install --save @blueprintjs/core`, and the warnings are now gone.

Am I installing the correct module for @material-ui?

Sean

DSpace version:  7.2-SNAPSHOT
  SCM revision:  fcc9f045a2f724db0bfa47b383c97050ea1943c2
SCM branch:  main
OS:  Linux(amd64) version 5.4.0-94-generic
  Applications:
 Discovery:  enabled.
   JRE:  Ubuntu version 11.0.13
   Ant version:  Apache Ant(TM) version 1.10.7 compiled on October 24 2019
 Maven version:  3.6.3

-- 
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%2BxAuhPPzt5HJtiDPpgy%2Bdf5BbojcY9BrtLYZWUDdAaD1xjaiw%40mail.gmail.com.

[dspace-tech] Solr: top downloads for a collection during time-frame

[Sean Carte]

How can I get a list of top downloads for a collection during a specified
time period from solr?

It looks like I should be able to modify the example query in the
documentation at https://wiki.lyrasis.org/display/DSDOC5x/SOLR+Statistics
to do what I want, but I don't know what to use as a facet.field, nor even
if this should work. This is my attempt, but it doesn't seem to produce a
different result to the original, which uses 'epersonid' as the facet.field:

/solr/statistics/select?indent=on=2.2=0=10=*%2Cscore=standard=standard===true=itemid=type:0+owningColl:9+isBot:false+time:[2021-01-01T00:00:00Z+TO+2021-11-30T00:00:00Z]

Sean
DSpace version:  CRIS-5.10.0-SNAPSHOT
  SCM revision:  67e7d010e7eda86925980b2a43581b9d4f4929a3
SCM branch:  dspace-5_x_x-cris
OS:  Linux(amd64) version 4.4.0-210-generic
  Applications:
 Discovery:  enabled.
   JRE:  Private Build version 1.8.0_292
   Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20 2018
 Maven version:  3.3.9

-- 
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%2BxAuhP05B0vYuUn5rjg%3D_aVdVx_6trb6-vyGc%3DQq56%3DoyiJGA%40mail.gmail.com.

[dspace-tech] Location of the extracted text bitstream file

[Sean Carte]

I'm trying to retrieve the extracted text bitstream associated with items.
Is there a way to get a list of them from the database?

So far, I've only been able to generate a list of all bitstreams with:

SELECT i.item_id, last_modified, owning_collection, internal_id,
t.text_value AS title
FROM item i
JOIN item2bundle i2b
ON i.item_id = i2b.item_id
JOIN bundle2bitstream b2b
ON b2b.bundle_id = i2b.bundle_id
JOIN bitstream b
ON b.bitstream_id = b2b.bitstream_id
JOIN metadatavalue d
ON d.resource_id = i.item_id
JOIN metadatavalue t
ON t.resource_id = i.item_id
WHERE in_archive = 't' AND withdrawn = 'f' AND discoverable = 't'
AND d.metadata_field_id = 11 AND d.text_value >= '2021-01' AND d.text_value
< '2021-12'
AND t.metadata_field_id = 64
ORDER BY owning_collection

That gives me a list including the internal_id, which I can use to
determine where the file is in the assetstore:
77274565375792968793874045792320511138 =
/dspace/assetstore/77/27/45/77274565375792968793874045792320511138

But I've noticed some gaps, like id 4117, which has both a PDF and an
extracted text bitstream, but in the assetstore, there's only the PDF in
that directory:
$ ls /dspace/assetstore/77/27/45/
77274565375792968793874045792320511138

How can I determine the location of the associated text extract bitstream
for that item?

Sean

DSpace version:  CRIS-5.10.0-SNAPSHOT
  SCM revision:  67e7d010e7eda86925980b2a43581b9d4f4929a3
SCM branch:  dspace-5_x_x-cris
OS:  Linux(amd64) version 4.4.0-210-generic
  Applications:
 Discovery:  enabled.
   JRE:  Private Build version 1.8.0_292
   Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20 2018
 Maven version:  3.3.9

-- 
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%2BxAuhPLrCGLxbUvCM1CgZN1FDjN8Cum7ZwrfA-yrcgVzC_83A%40mail.gmail.com.

Re: [dspace-tech] DSpace 7 CORS Error

[Sean Carte]

Thanks, Tim.

Sean

On Thu, 26 Aug 2021, 18:34 Tim Donohue,  wrote:

> Hi Sean,
>
> The problem is not obvious to me based on the information you've provided
> to us.  Just to verify...
>
>- In your frontend configs (environment.*.ts)
>   - UI section should likely say localhost, as this is where your
>   Node/Angular app is running locally. This is the only setting of these 
> that
>   usually is a localhost (non-public) URL, as this setting is used to 
> tell *Node
>   *where to start/run your app.
>   - REST section should be the public URL of REST, as this is the URL
>   that the Angular app will use to communicate with backend.
>- In your backend configs (local.cfg)
>   - dspace.ui.url should be the public URL of Angular UI, as that way
>   the REST API can validate responses properly coming any user who 
> accesses
>   your UI.
>   - dspace.server.url should be the public URL of REST (same as REST
>   section on backend)
>
> Your proxy settings look reasonable as well.
>
> I'd recommend looking for anything odd in logs of Apache or Tomcat or
> DSpace.  Maybe there's something else going on that you haven't discovered
> yet?  Something is definitely off here, and it's not obvious to me what it
> may be...that makes me suspect there may be an error somewhere that you
> haven't found.
>
> More tips can be found at
>
>-
>
> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>-
>
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
>
>
> Tim
>
> --
> *From:* Sean Carte 
> *Sent:* Thursday, August 26, 2021 2:32 AM
> *To:* Tim Donohue 
> *Cc:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] DSpace 7 CORS Error
>
> Thanks, Tim. I did try using the public URL in local.cfg, but then
> reverted to using localhost:4000 as I thought the proxy would expect to
> find dspace on localhost:4000. Also, I thought the rest.cors.allow-origins
> would let me use other origins (
> https://wiki.lyrasis.org/display/DSDOC7x/REST+API -- linked to from the
> CORS error part of the documentation).
>
> As you suggest, I've changed dspace.ui.url to:
>
> dspace.ui.url = https://dev-ir.dut.ac.za
>
> restarted tomcat, but I still have the same behaviour. I can log in
> directly to the backend on port 8080, but using the Angular UI or the
> /server endpoint results in CORS errors.
>
> I also tried changing environment.prod.ts as follows:
>
>   ui: {
>   ssl: false,
>   //host: 'localhost',
>   host: 'dev-ir.dut.ac.za',
>   port: 4000,
>   nameSpace: '/'
>   },
>
> That allows me to log in at
>
> https://dev-ir.dut.ac.za/server/
>
> However, I get a 503 at
>
> https://dev-ir.dut.ac.za/home
>
> I think that makes sense because the proxy is redirecting / to
> localhost:4000, so ui should be host: 'localhost'. But now I'm stuck.
>
> These are the lines for the proxy:
>
> ProxyPass /server http://localhost:8080/server
> ProxyPassReverse /server http://localhost:8080/server
> ProxyPass / http://localhost:4000/
> ProxyPassReverse / http://localhost:4000/
>
> Sean
>
> On Wed, 25 Aug 2021 at 17:00, Tim Donohue  wrote:
>
> Hi Sean,
>
> Your "dspace.ui.url" setting on the backend is incorrect.  This MUST be
> the public URL of the UI...and it appears you are publicly accesing the UI
> using a different URL in your browser.
>
> When you do this, the backend will throw a CORS error because it ONLY
> trusts clients listed in either "dspace.ui.url" or
> "rest.cors.allowed-origins" configurations.
>
> Currently, because you've set "dspace.ui.url = http://localhost:4000;,
> your backend will only trust requests that come directly from
> http://localhost:4000/ (meaning this must be the exact URL you type into
> your browser)
>
> More info on this behavior can also be found in the "Common Installation
> Issues" section of our install guide at:
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-%22CORSerror%22or%22InvalidCORSrequest%22
>
> Tim
>
> --
> *From:* dspace-tech@googlegroups.com  on
> behalf of Sean Carte 
> *Sent:* Wednesday, August 25, 2021 9:25 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] DSpace 7 CORS Error
>
> I am able to log into the backend at:
>
> http://dev-ir.dut.ac.za:8080/server/
>
> But using the Angular UI and
>
> https://dev-ir.dut.ac.za/server/login.html
>
> resul

Re: [dspace-tech] DSpace 7 CORS Error

[Sean Carte]

Thanks, Tim. I did try using the public URL in local.cfg, but then reverted
to using localhost:4000 as I thought the proxy would expect to find dspace
on localhost:4000. Also, I thought the rest.cors.allow-origins would let me
use other origins (https://wiki.lyrasis.org/display/DSDOC7x/REST+API --
linked to from the CORS error part of the documentation).

As you suggest, I've changed dspace.ui.url to:

dspace.ui.url = https://dev-ir.dut.ac.za

restarted tomcat, but I still have the same behaviour. I can log in
directly to the backend on port 8080, but using the Angular UI or the
/server endpoint results in CORS errors.

I also tried changing environment.prod.ts as follows:

  ui: {
  ssl: false,
  //host: 'localhost',
  host: 'dev-ir.dut.ac.za',
  port: 4000,
  nameSpace: '/'
  },

That allows me to log in at

https://dev-ir.dut.ac.za/server/

However, I get a 503 at

https://dev-ir.dut.ac.za/home

I think that makes sense because the proxy is redirecting / to
localhost:4000, so ui should be host: 'localhost'. But now I'm stuck.

These are the lines for the proxy:

ProxyPass /server http://localhost:8080/server
ProxyPassReverse /server http://localhost:8080/server
ProxyPass / http://localhost:4000/
ProxyPassReverse / http://localhost:4000/

Sean

On Wed, 25 Aug 2021 at 17:00, Tim Donohue  wrote:

> Hi Sean,
>
> Your "dspace.ui.url" setting on the backend is incorrect.  This MUST be
> the public URL of the UI...and it appears you are publicly accesing the UI
> using a different URL in your browser.
>
> When you do this, the backend will throw a CORS error because it ONLY
> trusts clients listed in either "dspace.ui.url" or
> "rest.cors.allowed-origins" configurations.
>
> Currently, because you've set "dspace.ui.url = http://localhost:4000;,
> your backend will only trust requests that come directly from
> http://localhost:4000/ (meaning this must be the exact URL you type into
> your browser)
>
> More info on this behavior can also be found in the "Common Installation
> Issues" section of our install guide at:
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-%22CORSerror%22or%22InvalidCORSrequest%22
>
> Tim
>
> --
> *From:* dspace-tech@googlegroups.com  on
> behalf of Sean Carte 
> *Sent:* Wednesday, August 25, 2021 9:25 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] DSpace 7 CORS Error
>
> I am able to log into the backend at:
>
> http://dev-ir.dut.ac.za:8080/server/
>
> But using the Angular UI and
>
> https://dev-ir.dut.ac.za/server/login.html
>
> results in a 403 with XHR errors.
>
> environment.prod.ts:
> export const environment = {
>   ui: {
>   ssl: false,
>   host: 'localhost',
>   port: 4000,
>   nameSpace: '/'
>   },
>   rest: {
>   ssl: true,
>   host: 'dev-ir.dut.ac.za',
>   port: 443,
>   nameSpace: '/server'
>   }
> };
>
> apache default-le-ssl.conf:
> ProxyPass /server http://localhost:8080/server
> ProxyPassReverse /server http://localhost:8080/server
> ProxyPass / http://localhost:4000/
> ProxyPassReverse / http://localhost:4000/
>
> local.cfg:
> dspace.server.url = https://dev-ir.dut.ac.za/server
> dspace.ui.url = http://localhost:4000
> rest.cors.allow-origins = ${dspace.ui.url}
> rest.cors.allow-origins = http://dev-ir.dut.ac.za
> rest.cors.allow-origins = http://dev-ir.dut.ac.za:4000
> rest.cors.allow-origins = https://dev-ir.dut.ac.za
> rest.cors.allow-origins = http://10.4.36.12
> rest.cors.allow-origins = http://10.4.36.12:4000
> rest.cors.allow-origins = https://10.4.36.12
>
> I'm not sure what's relevant from the browser's inspector window, but this
> is what I have after trying to log in with the Angular UI:
>
> [image: Selection_022.png]
> POST
> scheme https
> host dev-ir.dut.ac.za
> filename /server/api/authn/login
>
> Address 10.4.36.12:443
> Status
> 403
> VersionHTTP/1.1
> Transferred447 B (20 B size)
> Referrer Policystrict-origin-when-cross-origin
>
> Response Headers:
> HTTP/1.1 403
> Date: Wed, 25 Aug 2021 14:11:39 GMT
> Server: Apache/2.4.41 (Ubuntu)
> Vary: Origin,Access-Control-Request-Method,Access-Control-Request-Headers
> X-Content-Type-Options: nosniff
> X-XSS-Protection: 1; mode=block
> Cache-Control: no-cache, no-store, max-age=0, must-revalidate
> Pragma: no-cache
> Expires: 0
> X-Frame-Options: DENY
> Keep-Alive: timeout=5, max=100
> Connection: Keep-Alive
> Transfer-Encoding: chunked
>
> Request Headers:
> POST /server/api/authn/login HTTP/1.1
> Host: dev-ir.dut.ac.za
> User-Agent: Mozilla/5.0 (X11; Ubuntu

[dspace-tech] DSpace 7 CORS Error

[Sean Carte]

I am able to log into the backend at:

http://dev-ir.dut.ac.za:8080/server/

But using the Angular UI and

https://dev-ir.dut.ac.za/server/login.html

results in a 403 with XHR errors.

environment.prod.ts:
export const environment = {
  ui: {
  ssl: false,
  host: 'localhost',
  port: 4000,
  nameSpace: '/'
  },
  rest: {
  ssl: true,
  host: 'dev-ir.dut.ac.za',
  port: 443,
  nameSpace: '/server'
  }
};

apache default-le-ssl.conf:
ProxyPass /server http://localhost:8080/server
ProxyPassReverse /server http://localhost:8080/server
ProxyPass / http://localhost:4000/
ProxyPassReverse / http://localhost:4000/

local.cfg:
dspace.server.url = https://dev-ir.dut.ac.za/server
dspace.ui.url = http://localhost:4000
rest.cors.allow-origins = ${dspace.ui.url}
rest.cors.allow-origins = http://dev-ir.dut.ac.za
rest.cors.allow-origins = http://dev-ir.dut.ac.za:4000
rest.cors.allow-origins = https://dev-ir.dut.ac.za
rest.cors.allow-origins = http://10.4.36.12
rest.cors.allow-origins = http://10.4.36.12:4000
rest.cors.allow-origins = https://10.4.36.12

I'm not sure what's relevant from the browser's inspector window, but this
is what I have after trying to log in with the Angular UI:

[image: Selection_022.png]
POST
scheme https
host dev-ir.dut.ac.za
filename /server/api/authn/login

Address 10.4.36.12:443
Status
403
VersionHTTP/1.1
Transferred447 B (20 B size)
Referrer Policystrict-origin-when-cross-origin

Response Headers:
HTTP/1.1 403
Date: Wed, 25 Aug 2021 14:11:39 GMT
Server: Apache/2.4.41 (Ubuntu)
Vary: Origin,Access-Control-Request-Method,Access-Control-Request-Headers
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-Frame-Options: DENY
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked

Request Headers:
POST /server/api/authn/login HTTP/1.1
Host: dev-ir.dut.ac.za
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:91.0) Gecko/20100101
Firefox/91.0
Accept: application/json, text/plain, */*
Accept-Language: en;q=1,en-US;q=0.1,en;q=0.09
Accept-Encoding: gzip, deflate, br
Content-Type: application/x-www-form-urlencoded
X-XSRF-TOKEN: 56f4015c-5256-4512-8861-12dacda7aae3
X-CORRELATION-ID: 352472e7-b842-4987-b223-961900a64746
X-REFERRER: /home
Content-Length: 43
Origin: https://dev-ir.dut.ac.za
Connection: keep-alive
Referer: https://dev-ir.dut.ac.za/home
Cookie: DSPACE-XSRF-COOKIE=56f4015c-5256-4512-8861-12dacda7aae3;
_fbp=fb.2.1611567268808.3166000;
__tawkuuid=e::dut.ac.za::X4iey+2XGFdXPDH6lKG4Ikr4yo9SdzTjom+Nd+69vueiUCsm4iQyTzbzsr6pAIEN::2;
_ga=GA1.3.923244129.1612793087;
__utma=97131402.923244129.1612793087.1624370603.1624440611.58;
__utmz=97131402.1620118111.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none);
cookieconsent_status=dismiss;
klaro-anonymous=%7B%22authentication%22%3Atrue%2C%22preferences%22%3Atrue%2C%22acknowledgement%22%3Atrue%2C%22google-analytics%22%3Atrue%7D;
_gid=GA1.3.1575206032.1629785492;
CORRELATION-ID=352472e7-b842-4987-b223-961900a64746; dsLanguage=en;
XSRF-TOKEN=56f4015c-5256-4512-8861-12dacda7aae3; dsRedirectUrl=/home
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
Pragma: no-cache
Cache-Control: no-cache

Please tell me where I've gone wrong.

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/CA%2BxAuhNk4FsYS1BJ3BaS9T3A9u7DRXv_JK5s9NvHWATaA0Ycsw%40mail.gmail.com.

Re: [dspace-tech] DSpace 7: 'Invalid email or password'

[Sean Carte]

Thanks, Tim. I did try using the IP address everywhere, and that didn't
work. But, as you point out, that would be because I wasn't using HTTPS.

As you also point out, it's right there in the instructions: '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).'

I must have read that a hundred times without taking it in.

I'll try again with the IP addresses and HTTPS.

Sean

On Wed, 18 Aug 2021 at 17:01, Tim Donohue  wrote:

> Hi Sean,
>
> It looks like your environment.prod.ts is using a "localhost" based URL
> for the REST API.  This means it will attempt to access your REST API on
> the *same machine *where you are running your web browser.
>
> In other words, a localhost URL for the REST API is only valid if you are
> in a development environment...where both the UI and REST API are running
> on your local machine & you are only accessing both via localhost URLs from
> that same machine.
>
> Since it sounds like you are accessing your REST API via a public IP
> address (10.4.36.43), you should be using that same public URL/IP address
> in your "rest" settings for environment.prod.ts.  Keep in mind, your REST
> API also MUST be running HTTPS if you plan to run it on a non-localhost
> URL.
>
> See the various "Common Installation Issues" here:
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
>
> Also, see step 16 of the Backend Installation instructions:
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-BackendInstallation
>
> Good luck!
> Tim
>
>
> --
> *From:* dspace-tech@googlegroups.com  on
> behalf of Sean Carte 
> *Sent:* Tuesday, August 17, 2021 8:21 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] DSpace 7: 'Invalid email or password'
>
> After installing DSpace 7, I created an administrator account, but am
> unable to log in using those credentials; I get the error: 'invalid email
> or password'.
>
> I am able to use those credentials to log into the HAL Browser, however.
>
> I'm using a VM on a remote server with the following URLs:
>
> http://10.4.36.43:8080/server/
> http://10.4.36.43
>
> I have Nginx configured to proxy port 4000.
>
> I checked the Network tab of Firefox's Dev Tools, and saw CORS Failed
> errors, and the DSpace installation documentation,
>
>- By default, the DSpace REST API / Backend will only trust the
>application at dspace.ui.url.  Therefore, you should first verify that
>your dspace.ui.url setting (in your local.cfg) exactly matches the
>*primary* *URL* of your User Interface (i.e. the URL you see in the
>browser).  This must be an exact match: mode (http vs https), domain, port,
>and subpath(s) all must match.
>- If you need to trust *additional* client applications / URLs, those
>MUST be added to the rest.cors.allowed-origins configuration. See REST
>API <https://wiki.lyrasis.org/display/DSDOC7x/REST+API> for details on
>this configuration.
>
> So I added these to the foot of my local.cfg and restarted tomcat:
>
> rest.cors.allow-origins = ${dspace.ui.url}
> rest.cors.allow-origins = http://localhost
> rest.cors.allow-origins = http://10.4.36.43:4000
> rest.cors.allow-origins = http://10.4.36.43
> rest.cors.allow-origins = http://localhost:8080
> rest.cors.allow-origins = localhost:8080
>
> But that doesn't seem to have helped:
>
> [image: Selection_021.png]
> These are my configurations:
>
> src/environments/environment.prod.ts:
> export const environment = {
>   ui: {
>   ssl: false,
>   host: 'localhost',
>   port: 4000,
>   nameSpace: '/'
>   },
>   rest: {
>   ssl: false,
>   host: 'localhost',
>   port: 8080,
>   nameSpace: '/server'
>   }
> };
>
> /dspace/config/local.cfg:
> dspace.dir=/dspace
> dspace.server.url = http://localhost:8080/server
> dspace.ui.url = http://localhost:4000
>
> /etc/nginx/sites-enabled/default:
> location / {
> proxy_pass  http://localhost:4000;
> proxy_http_version 1.1;
> proxy_set_header Upgrade $http_upgrade;
> proxy_set_header Connection ‘upgrade’;
> proxy_set_header Host $host;
> proxy_cache_bypass $http_upgrade;
> proxy_set_header X-Real-IP $remote_addr;
> proxy_set_header HOST $http_host;
> proxy_set_header X-NginX-Proxy true;
> proxy_set_hea

[dspace-tech] DSpace 7: 'Invalid email or password'

[Sean Carte]

After installing DSpace 7, I created an administrator account, but am
unable to log in using those credentials; I get the error: 'invalid email
or password'.

I am able to use those credentials to log into the HAL Browser, however.

I'm using a VM on a remote server with the following URLs:

http://10.4.36.43:8080/server/
http://10.4.36.43

I have Nginx configured to proxy port 4000.

I checked the Network tab of Firefox's Dev Tools, and saw CORS Failed
errors, and the DSpace installation documentation,

   - By default, the DSpace REST API / Backend will only trust the
   application at dspace.ui.url.  Therefore, you should first verify that
   your dspace.ui.url setting (in your local.cfg) exactly matches the
   *primary* *URL* of your User Interface (i.e. the URL you see in the
   browser).  This must be an exact match: mode (http vs https), domain, port,
   and subpath(s) all must match.
   - If you need to trust *additional* client applications / URLs, those
   MUST be added to the rest.cors.allowed-origins configuration. See REST
   API  for details on
   this configuration.

So I added these to the foot of my local.cfg and restarted tomcat:

rest.cors.allow-origins = ${dspace.ui.url}
rest.cors.allow-origins = http://localhost
rest.cors.allow-origins = http://10.4.36.43:4000
rest.cors.allow-origins = http://10.4.36.43
rest.cors.allow-origins = http://localhost:8080
rest.cors.allow-origins = localhost:8080

But that doesn't seem to have helped:

[image: Selection_021.png]
These are my configurations:

src/environments/environment.prod.ts:
export const environment = {
  ui: {
  ssl: false,
  host: 'localhost',
  port: 4000,
  nameSpace: '/'
  },
  rest: {
  ssl: false,
  host: 'localhost',
  port: 8080,
  nameSpace: '/server'
  }
};

/dspace/config/local.cfg:
dspace.dir=/dspace
dspace.server.url = http://localhost:8080/server
dspace.ui.url = http://localhost:4000

/etc/nginx/sites-enabled/default:
location / {
proxy_pass  http://localhost:4000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection ‘upgrade’;
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header HOST $http_host;
proxy_set_header X-NginX-Proxy true;
proxy_set_header X-Forwarded-Proto $scheme;
}

Any ideas where I've gone wrong?

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/CA%2BxAuhP%3DypdwoXdD%3DVjxJT%3D%3DF3abRkDPMUdPkr2q9DSQ2hGX%3Dg%40mail.gmail.com.

[dspace-tech] DSpace 6: Add metadata fields to simple item record page

[Sean Carte]

Is it possible to change what metadata is displayed on the simple item
record page in DSpace 6 (JSPUI and XMLUI)?

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/CA%2BxAuhNDgiwuMqSLbHp8%3DH-M2-xGvm7fBuS0H0eRBFdAJ3XMDA%40mail.gmail.com.

Re: [dspace-tech] Re: OAI 500 error

[Sean Carte]

I would expect so.

Sean

On Wed, 2 Jun 2021 at 16:35, ottawad...@gmail.com 
wrote:

> Hi, just wondering if this xalan version pom.xml change requires a rebuild
> or not? (using Dspace 6.3 JSPUI)
>
> On Wednesday, February 24, 2021 at 12:51:41 AM UTC-5 michelsa...@gmail.com
> wrote:
>
>> Hi,
>>
>> We faced the same problem one year ago and it's a known bug caused from
>> the library Xalan 2.7.1 As there is no updates on that library, the only
>> solution I found is to use an older one (Xalan 2.7.0) instead of the
>> "problematic" 2.7.1 if you need to use OAI with that encoding. You have to
>> edit the file pom.xml and replace it in this section:
>> 
>> xalan
>> xalan
>> 2.7.0
>> 
>>
>> I posted a pull request on DSpace-CRIS with that change (
>> https://github.com/4Science/DSpace/pull/101)
>>
>> El lunes, 15 de febrero de 2021 a las 8:43:26 UTC, sean@gmail.com
>> escribió:
>>
>>> Some abstracts in our repository contain what I assume are UTF-8
>>> characters, like '휌'. They display correctly in the HTML interface, but
>>> cause an exception when retrieving the record via OAI-PMH:
>>>
>>> java.io.IOException: 
>>> com.lyncode.xoai.dataprovider.exceptions.WritingXmlException: Error trying 
>>> to output '>> xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/; 
>>> xmlns:doc="http://www.lyncode.com/xoai; 
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
>>> xmlns:dc="http://purl.org/dc/elements/1.1/; 
>>> xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ 
>>> http://www.openarchives.org/OAI/2.0/oai_dc.xsd;>
>>> ...
>>> Ionic Liquids (ILs) are relatively newly formed types of 
>>> solvents. As part of ongoing research, research groups and industries are 
>>> focusing on solvents classified as ionic liquids, which have a low melting 
>>> point,and they have been given great attention focusing on their 
>>> thermophysical properties and applications. In order to utilize or 
>>> industrially exploit these types of solvents, the understanding of 
>>> intermolecular interactions and properties of pure liquids and their 
>>> mixtures is important. Thermophysical properties of ionic liquid mixtures, 
>>> especially density, viscosity and speed of sound are measured as a function 
>>> of temperature. Accurate analysis on thermophysical properties of ionic 
>>> liquids is more of paramount interest as they indicate the transformation 
>>> of ionic liquids from small laboratory level to large-scale industrial 
>>> implementation.In this study, new data for the binary mixtures containing 
>>> {trihexyltetradecylphosphonium chloride ([P+14, 6, 6, 6] [Cl-]) IL and 
>>> propanoic acid (PA)} and {1-ethyl-3-methylimidazolium tetrafluoroborate 
>>> ([Emim][BF4]) + benzaldehyde or ethyl acetoacetate} were investigated under 
>>> atmospheric pressure (p equivalent to 0.1 MPa) and at temperatures (293.15 
>>> to 313.15) K. Densities ()
>>> ...
>>> '
>>> 
>>> org.dspace.xoai.services.impl.cache.DSpaceXOAICacheService.store(DSpaceXOAICacheService.java:114)
>>> 
>>> org.dspace.xoai.controller.DSpaceOAIDataProvider.contextAction(DSpaceOAIDataProvider.java:104)
>>> sun.reflect.GeneratedMethodAccessor633.invoke(Unknown Source)
>>> 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> java.lang.reflect.Method.invoke(Method.java:498)
>>> 
>>> org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:215)
>>> 
>>> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132)
>>> 
>>> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)
>>> 
>>> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:743)
>>> 
>>> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:672)
>>> 
>>> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:82)
>>> 
>>> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:933)
>>> 
>>> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:867)
>>> 
>>> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:951)
>>> 
>>> org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:842)
>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:622)
>>> 
>>> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:827)
>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
>>> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>>>
>>> In the error message, the document's abstract,'휌'. has been encoded as
>>> '', but seems 

Re: [dspace-tech] Re: Tomcat 9 on Ubuntu 18.04

[Sean Carte]

Thank you, diegoucha!

As someone else in that thread commented, I had no idea that systemd could
do that.

Sean

On Thu, 20 May 2021 at 18:01, dieg...@gmail.com  wrote:

> You can find the solution in the "Edit" section of the most voted question
> in
> https://stackoverflow.com/questions/56827735/how-to-allow-tomcat-war-app-to-write-in-folder
> Tomcat 9 only writes to specific folders. You have to add new dirs to
> 'ReadWritePaths' directive, in your case "/dspace/log"
>
> On Thursday, May 20, 2021 at 8:20:32 AM UTC-3 sean@gmail.com wrote:
>
>> I'm having trouble getting tomcat 9 to work with dspace, yet I have no
>> problems with tomcat 8. This is on Ubuntu 18.04.
>>
>> When using tomcat 9, no log files are created in /dspace/log and the
>> dspace GUI indicates an internal error.
>>
>> This is my (working) configuration for tomcat 8:
>>
>> ls -ld /dspace/
>> drwxr-xr-x 16 tomcat8 tomcat8 4096 May 20 11:07 /dspace/
>>
>> /etc/default/tomcat8
>> TOMCAT8_USER=tomcat8
>> TOMCAT8_GROUP=tomcat8
>> JAVA_OPTS="-Djava.awt.headless=true -Xmx1024m -Xms64M
>> -XX:+UseConcMarkSweepGC -Dfile.encoding=UTF-8"
>> #TOMCAT8_SECURITY=no
>>
>> For tomcat 9, the user is 'tomcat', so this is what I have for tomcat 9:
>>
>> ls -ld /dspace/
>> drwxr-xr-x 16 tomcat tomcat 4096 May 20 11:07 /dspace/
>>
>> /etc/default/tomcat9
>> JAVA_OPTS="-Djava.awt.headless=true -Xmx1024m -Xms64M
>> -XX:+UseConcMarkSweepGC -Dfile.encoding=UTF-8"
>> SECURITY_MANAGER=false
>>
>> I tried adding (variations of)
>> TOMCAT9_USER=tomcat
>> TOMCAT9_GROUP=tomcat
>> to /etc/default/tomcat9, but that hasn't made any difference.
>>
>> The contexts are identical (I copied /etc/tomcat9/Catalina/localost/*.xml
>> to /etc/tomcat8/Catalina/localhost/):
>> /etc/tomcat9/Catalina/localhost/ROOT.xml
>> 
>> > docBase="/dspace/webapps/jspui"
>> reloadable="true"
>> cachingAllowed="false"
>> />
>>
>> /etc/tomcat9/Catalina/localhost/solr.xml
>> 
>> > docBase="/dspace/webapps/solr"
>> reloadable="true"
>> cachingAllowed="false"
>> />
>>
>> /etc/tomcat9/Catalina/localhost/jspui.xml
>> 
>> > docBase="/dspace/webapps/jspui"
>> reloadable="true"
>> cachingAllowed="false"
>> />
>>
>> No errors are reported in /var/log/tomcat9/catalina.2021-05-20.log, yet
>> it seems like tomcat9 does not have access to /dspace, and I can't figure
>> out why.
>>
>> Does anybody know where I've gone wrong?
>>
>> Sean
>>
> --
> 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/6eac177e-32f1-4a7a-88ea-aab05d959743n%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/CA%2BxAuhNTt_bm94MghFWemNv4HJAnqDqwewLXB-PLzHM2N7PMfA%40mail.gmail.com.

[dspace-tech] Tomcat 9 on Ubuntu 18.04

[Sean Carte]

I'm having trouble getting tomcat 9 to work with dspace, yet I have no
problems with tomcat 8. This is on Ubuntu 18.04.

When using tomcat 9, no log files are created in /dspace/log and the dspace
GUI indicates an internal error.

This is my (working) configuration for tomcat 8:

ls -ld /dspace/
drwxr-xr-x 16 tomcat8 tomcat8 4096 May 20 11:07 /dspace/

/etc/default/tomcat8
TOMCAT8_USER=tomcat8
TOMCAT8_GROUP=tomcat8
JAVA_OPTS="-Djava.awt.headless=true -Xmx1024m -Xms64M
-XX:+UseConcMarkSweepGC -Dfile.encoding=UTF-8"
#TOMCAT8_SECURITY=no

For tomcat 9, the user is 'tomcat', so this is what I have for tomcat 9:

ls -ld /dspace/
drwxr-xr-x 16 tomcat tomcat 4096 May 20 11:07 /dspace/

/etc/default/tomcat9
JAVA_OPTS="-Djava.awt.headless=true -Xmx1024m -Xms64M
-XX:+UseConcMarkSweepGC -Dfile.encoding=UTF-8"
SECURITY_MANAGER=false

I tried adding (variations of)
TOMCAT9_USER=tomcat
TOMCAT9_GROUP=tomcat
to /etc/default/tomcat9, but that hasn't made any difference.

The contexts are identical (I copied /etc/tomcat9/Catalina/localost/*.xml
to /etc/tomcat8/Catalina/localhost/):
/etc/tomcat9/Catalina/localhost/ROOT.xml



/etc/tomcat9/Catalina/localhost/solr.xml



/etc/tomcat9/Catalina/localhost/jspui.xml



No errors are reported in /var/log/tomcat9/catalina.2021-05-20.log, yet it
seems like tomcat9 does not have access to /dspace, and I can't figure out
why.

Does anybody know where I've gone wrong?

Sean

-- 
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/CA%2BxAuhOa%2B5fY5%3D1v0xZZk%2BsEMaVWFo%2BxWK%2BNnUGBQBKSqn%3DrjQ%40mail.gmail.com.

[dspace-tech] Warning and error after DSpace-CRIS 5.10 upgrade

[Sean Carte]

After upgrading my DSpace-CRIS 5.10 repository to the latest code from
github, I now see these messages repeated in the logs:

2021-05-19 09:21:30,581 WARN  org.dspace.core.PluginManager @ Cannot find
named plugin for interface=org.dspace.content.authority.ChoiceAuthority,
name="null"
2021-05-19 09:21:30,582 ERROR
org.dspace.content.authority.ChoiceAuthorityManager @ Illegal configuration
property: choices.extralookup.dc_contributor_author

I have this in my dspace.cfg:

choices.extralookup.dc_contributor_author = true

And it was that way previously, but this is the first time I'm seeing these
messages.

Has something gone wrong with the upgrade?

Sean

-- 
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/CA%2BxAuhP7TZWQCa2ei%3DLLKD%3DsZ4HbYTiFjo6cUyELLiCME_L1uw%40mail.gmail.com.

Re: [dspace-tech] Restrict access to logged-in users only

[Sean Carte]

I've only been restricting access in 6.3, but I don't see why
login.specialgroup wouldn't work in DSpace-CRIS 5.10. The type of
authentication used shouldn't matter either.

On Wed, 17 Feb 2021 at 12:57, Marc  wrote:

> Dear José and group,
>
> Hope you don’t mind me hijacking this thread. Would setting the
> login.specialgroup work for DSpace CRIS 5.10 using ORCID as the
> authentication method? I basically just want to restrict access to the
> default_bitstream_read, to logged on users. Meaning that you have to be
> logged in to be able to download files.
>
> Thank you
>
> Marc
>
> On 3 Feb 2021, at 15:58, José Geraldo wrote:
>
> Use the database to change or add permission.
>
> The table used is resourcepolicy.
>
> Updating the epersongroup_id to id of the special group created e o filtro
> por action_id.
>
> action_id:
>
> 0 read
> 1 write
> 3 add
> 4 remove
> 9 default_bitstream_read
> 10 default_item_read
> 11 admin
>
> Em qua., 3 de fev. de 2021 às 11:52, Sean Carte 
> escreveu:
>
>> I was hoping for some guidance on that. I did look at the tables, but
>> wasn't able to find anything obviously related to access rights.
>>
>> Or did you mean that I should use the database to move items from the
>> collection? That might work.
>>
>> On Wed, 3 Feb 2021 at 15:11, José Geraldo  wrote:
>>
>>> Another option would be to backup your database and make changes to the
>>> database.
>>>
>>> Em qua., 3 de fev. de 2021 às 04:13, Sean Carte 
>>> escreveu:
>>>
>>>> For most collections, using the wildcard policy admin tool has worked
>>>> very well, and I have been able to restrict their bitstreams to logged-in
>>>> users. However, I have two collections with over 1000 items. For one of
>>>> these, with 1688 items, I was not able to remove the anonymous read access;
>>>> the browser reports an internal error, but there's nothing in the tomcat or
>>>> dspace logs. Another collection, of 1012 items, allowed me to remove
>>>> anonymous read access, but I have not been able to add READ access for the
>>>> logged-in group.
>>>>
>>>> Apart from moving hundreds of items out of those collections, to reduce
>>>> their size, does anybody have any suggestions on how I should proceed?
>>>>
>>>> DSpace version:  6.3
>>>> XMLUI
>>>> Mirage2 theme
>>>>
>>>> On Fri, 29 Jan 2021 at 20:48, Sean Carte  wrote:
>>>>
>>>>> Thanks again, José; you've been extremely helpful.
>>>>>
>>>>> On Fri, 29 Jan 2021 at 15:43, José Geraldo  wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Items accepted in a collection inherit the associated authorization
>>>>>> policies DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ, which become READ
>>>>>> policies for the item and its attachments.
>>>>>>
>>>>>> However, when changing the default policies for a collection, once
>>>>>> items are accepted, the policies for existing items will not be changed
>>>>>> automatically.
>>>>>>
>>>>>> Soon, a user, without logging in and in possession of the link to one
>>>>>> of the items in the collection, will have access to the item and its
>>>>>> contents.
>>>>>>
>>>>>> To get around this point, you will need to change the permissions of
>>>>>> the items in the collection using the Policy Administration Tool to make
>>>>>> them accessible only to logged-in users.
>>>>>>
>>>>>> For each item in a collection, there is only one READ policy
>>>>>> configured for the Anonymous group.
>>>>>>
>>>>>> However, the tool does not have the option to edit policies, having
>>>>>> only the options to add and delete policies.
>>>>>>
>>>>>> Therefore, it will be necessary to first delete the policies for
>>>>>> items and binary files (attachments) and then create new READ policies
>>>>>> linked to the special group for them.
>>>>>>
>>>>>> This process is done one collection at a time, if you need to apply
>>>>>> to all collections, a suggestion would be to apply it to the database.
>>>>>>
>>>>>> Em sex., 29 de jan. de 2021 às 04:09, Sean Carte <
>>&

[dspace-tech] OAI 500 error

[Sean Carte]

Some abstracts in our repository contain what I assume are UTF-8
characters, like '휌'. They display correctly in the HTML interface, but
cause an exception when retrieving the record via OAI-PMH:

java.io.IOException:
com.lyncode.xoai.dataprovider.exceptions.WritingXmlException: Error
trying to output 'http://www.openarchives.org/OAI/2.0/oai_dc/;
xmlns:doc="http://www.lyncode.com/xoai;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:dc="http://purl.org/dc/elements/1.1/;
xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd;>
...
Ionic Liquids (ILs) are relatively newly formed types
of solvents. As part of ongoing research, research groups and
industries are focusing on solvents classified as ionic liquids, which
have a low melting point,and they have been given great attention
focusing on their thermophysical properties and applications. In order
to utilize or industrially exploit these types of solvents, the
understanding of intermolecular interactions and properties of pure
liquids and their mixtures is important. Thermophysical properties of
ionic liquid mixtures, especially density, viscosity and speed of
sound are measured as a function of temperature. Accurate analysis on
thermophysical properties of ionic liquids is more of paramount
interest as they indicate the transformation of ionic liquids from
small laboratory level to large-scale industrial implementation.In
this study, new data for the binary mixtures containing
{trihexyltetradecylphosphonium chloride ([P+14, 6, 6, 6] [Cl-]) IL and
propanoic acid (PA)} and {1-ethyl-3-methylimidazolium
tetrafluoroborate ([Emim][BF4]) + benzaldehyde or ethyl acetoacetate}
were investigated under atmospheric pressure (p equivalent to 0.1 MPa)
and at temperatures (293.15 to 313.15) K. Densities ()
...
'

org.dspace.xoai.services.impl.cache.DSpaceXOAICacheService.store(DSpaceXOAICacheService.java:114)

org.dspace.xoai.controller.DSpaceOAIDataProvider.contextAction(DSpaceOAIDataProvider.java:104)
sun.reflect.GeneratedMethodAccessor633.invoke(Unknown Source)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)

org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:215)

org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132)

org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)

org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:743)

org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:672)

org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:82)

org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:933)

org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:867)

org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:951)

org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:842)
javax.servlet.http.HttpServlet.service(HttpServlet.java:622)

org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:827)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

In the error message, the document's abstract,'휌'. has been encoded as
'', but seems to be causing the exception.

If I remove the abstract and wait a day (presumably for re-indexing), I can
access the record via OAI-PMH.

Is there a way to include these symbols that will not cause the exception?

I do have 'URIEncoding="UTF-8"' in my port 8080 connector definition in
server.xml.

DSpace version:  CRIS-5.10.0-SNAPSHOT
  SCM revision:  8390fec2945050541427ef1249dbbbd56b1ccdc4
SCM branch:  fix-sword
OS:  Linux(amd64) version 4.4.0-198-generic
  Applications:
 Discovery:  enabled.
   JRE:  Private Build version 1.8.0_282
   Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20 2018
 Maven version:  3.3.9

-- 
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 

Re: [dspace-tech] Restrict access to logged-in users only

[Sean Carte]

Thanks yet again, José! After much testing, I was able to modify the rights
to all items in the repository. I would not have been able to get this
right without your assistance.

On Wed, 3 Feb 2021 at 17:58, José Geraldo  wrote:

> Use the database to change or add permission.
>
> The table used is resourcepolicy.
>
> Updating the epersongroup_id to id of the special group created e o filtro
> por action_id.
>
> action_id:
>
> 0 read
> 1 write
> 3 add
> 4 remove
> 9 default_bitstream_read
> 10 default_item_read
> 11 admin
>
> Em qua., 3 de fev. de 2021 às 11:52, Sean Carte 
> escreveu:
>
>> I was hoping for some guidance on that. I did look at the tables, but
>> wasn't able to find anything obviously related to access rights.
>>
>> Or did you mean that I should use the database to move items from the
>> collection? That might work.
>>
>> On Wed, 3 Feb 2021 at 15:11, José Geraldo  wrote:
>>
>>> Another option would be to backup your database and make changes to the
>>> database.
>>>
>>> Em qua., 3 de fev. de 2021 às 04:13, Sean Carte 
>>> escreveu:
>>>
>>>> For most collections, using the wildcard policy admin tool has worked
>>>> very well, and I have been able to restrict their bitstreams to logged-in
>>>> users. However, I have two collections with over 1000 items. For one of
>>>> these, with 1688 items, I was not able to remove the anonymous read access;
>>>> the browser reports an internal error, but there's nothing in the tomcat or
>>>> dspace logs. Another collection, of 1012 items, allowed me to remove
>>>> anonymous read access, but I have not been able to add READ access for the
>>>> logged-in group.
>>>>
>>>> Apart from moving hundreds of items out of those collections, to reduce
>>>> their size, does anybody have any suggestions on how I should proceed?
>>>>
>>>> DSpace version:  6.3
>>>> XMLUI
>>>> Mirage2 theme
>>>>
>>>> On Fri, 29 Jan 2021 at 20:48, Sean Carte  wrote:
>>>>
>>>>> Thanks again, José; you've been extremely helpful.
>>>>>
>>>>> On Fri, 29 Jan 2021 at 15:43, José Geraldo  wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Items accepted in a collection inherit the associated authorization
>>>>>> policies DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ, which become READ
>>>>>> policies for the item and its attachments.
>>>>>>
>>>>>> However, when changing the default policies for a collection, once
>>>>>> items are accepted, the policies for existing items will not be changed
>>>>>> automatically.
>>>>>>
>>>>>> Soon, a user, without logging in and in possession of the link to one
>>>>>> of the items in the collection, will have access to the item and its
>>>>>> contents.
>>>>>>
>>>>>> To get around this point, you will need to change the permissions of
>>>>>> the items in the collection using the Policy Administration Tool to make
>>>>>> them accessible only to logged-in users.
>>>>>>
>>>>>> For each item in a collection, there is only one READ policy
>>>>>> configured for the Anonymous group.
>>>>>>
>>>>>> However, the tool does not have the option to edit policies, having
>>>>>> only the options to add and delete policies.
>>>>>>
>>>>>> Therefore, it will be necessary to first delete the policies for
>>>>>> items and binary files (attachments) and then create new READ policies
>>>>>> linked to the special group for them.
>>>>>>
>>>>>> This process is done one collection at a time, if you need to apply
>>>>>> to all collections, a suggestion would be to apply it to the database.
>>>>>>
>>>>>> Em sex., 29 de jan. de 2021 às 04:09, Sean Carte <
>>>>>> sean.ca...@gmail.com> escreveu:
>>>>>>
>>>>>>> Using the login.specialgroup, along with removing default read
>>>>>>> access to the collections, does restrict access to collections listed on
>>>>>>> the home page. However, anonymous access is still available to items 
>>>>>>> made
>>>>>>> available by 

Re: [dspace-tech] Restrict access to logged-in users only

[Sean Carte]

I was hoping for some guidance on that. I did look at the tables, but
wasn't able to find anything obviously related to access rights.

Or did you mean that I should use the database to move items from the
collection? That might work.

On Wed, 3 Feb 2021 at 15:11, José Geraldo  wrote:

> Another option would be to backup your database and make changes to the
> database.
>
> Em qua., 3 de fev. de 2021 às 04:13, Sean Carte 
> escreveu:
>
>> For most collections, using the wildcard policy admin tool has worked
>> very well, and I have been able to restrict their bitstreams to logged-in
>> users. However, I have two collections with over 1000 items. For one of
>> these, with 1688 items, I was not able to remove the anonymous read access;
>> the browser reports an internal error, but there's nothing in the tomcat or
>> dspace logs. Another collection, of 1012 items, allowed me to remove
>> anonymous read access, but I have not been able to add READ access for the
>> logged-in group.
>>
>> Apart from moving hundreds of items out of those collections, to reduce
>> their size, does anybody have any suggestions on how I should proceed?
>>
>> DSpace version:  6.3
>> XMLUI
>> Mirage2 theme
>>
>> On Fri, 29 Jan 2021 at 20:48, Sean Carte  wrote:
>>
>>> Thanks again, José; you've been extremely helpful.
>>>
>>> On Fri, 29 Jan 2021 at 15:43, José Geraldo  wrote:
>>>
>>>> Hi,
>>>>
>>>> Items accepted in a collection inherit the associated authorization
>>>> policies DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ, which become READ
>>>> policies for the item and its attachments.
>>>>
>>>> However, when changing the default policies for a collection, once
>>>> items are accepted, the policies for existing items will not be changed
>>>> automatically.
>>>>
>>>> Soon, a user, without logging in and in possession of the link to one
>>>> of the items in the collection, will have access to the item and its
>>>> contents.
>>>>
>>>> To get around this point, you will need to change the permissions of
>>>> the items in the collection using the Policy Administration Tool to make
>>>> them accessible only to logged-in users.
>>>>
>>>> For each item in a collection, there is only one READ policy configured
>>>> for the Anonymous group.
>>>>
>>>> However, the tool does not have the option to edit policies, having
>>>> only the options to add and delete policies.
>>>>
>>>> Therefore, it will be necessary to first delete the policies for items
>>>> and binary files (attachments) and then create new READ policies linked to
>>>> the special group for them.
>>>>
>>>> This process is done one collection at a time, if you need to apply to
>>>> all collections, a suggestion would be to apply it to the database.
>>>>
>>>> Em sex., 29 de jan. de 2021 às 04:09, Sean Carte 
>>>> escreveu:
>>>>
>>>>> Using the login.specialgroup, along with removing default read access
>>>>> to the collections, does restrict access to collections listed on the home
>>>>> page. However, anonymous access is still available to items made available
>>>>> by Discovery. That is, in the 'Recently Added' section, or via search, or
>>>>> the browse lists.
>>>>>
>>>>> Removing anonymous read access from items' bitstreams and replacing it
>>>>> with read access for the authenticated special group does work, but I'm
>>>>> going to have to repeat this process every time a new item is added. Also,
>>>>> the wildcard policy admin tool seems to time out when used on multiple
>>>>> collections, or even large collections (> ~1000), in which case the items
>>>>> are not modified.
>>>>>
>>>>> I suppose I could modify the UI to remove the ability to use
>>>>> discovery, etc., but that rather defeats the purpose of using DSpace.
>>>>>
>>>>> Is there a better approach?
>>>>>
>>>>> My goal is to have all items available to logged-in users, but nothing
>>>>> available to anonymous users.
>>>>>
>>>>> DSpace version:  6.3
>>>>> XMLUI
>>>>> Mirage2 theme
>>>>>
>>>>> On Wed, 27 Jan 2021 at 15:28, Sean Carte  wrote:
>>>>>
>>

Re: [dspace-tech] Restrict access to logged-in users only

[Sean Carte]

For most collections, using the wildcard policy admin tool has worked very
well, and I have been able to restrict their bitstreams to logged-in users.
However, I have two collections with over 1000 items. For one of these,
with 1688 items, I was not able to remove the anonymous read access; the
browser reports an internal error, but there's nothing in the tomcat or
dspace logs. Another collection, of 1012 items, allowed me to remove
anonymous read access, but I have not been able to add READ access for the
logged-in group.

Apart from moving hundreds of items out of those collections, to reduce
their size, does anybody have any suggestions on how I should proceed?

DSpace version:  6.3
XMLUI
Mirage2 theme

On Fri, 29 Jan 2021 at 20:48, Sean Carte  wrote:

> Thanks again, José; you've been extremely helpful.
>
> On Fri, 29 Jan 2021 at 15:43, José Geraldo  wrote:
>
>> Hi,
>>
>> Items accepted in a collection inherit the associated authorization
>> policies DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ, which become READ
>> policies for the item and its attachments.
>>
>> However, when changing the default policies for a collection, once items
>> are accepted, the policies for existing items will not be changed
>> automatically.
>>
>> Soon, a user, without logging in and in possession of the link to one of
>> the items in the collection, will have access to the item and its contents.
>>
>> To get around this point, you will need to change the permissions of the
>> items in the collection using the Policy Administration Tool to make them
>> accessible only to logged-in users.
>>
>> For each item in a collection, there is only one READ policy configured
>> for the Anonymous group.
>>
>> However, the tool does not have the option to edit policies, having only
>> the options to add and delete policies.
>>
>> Therefore, it will be necessary to first delete the policies for items
>> and binary files (attachments) and then create new READ policies linked to
>> the special group for them.
>>
>> This process is done one collection at a time, if you need to apply to
>> all collections, a suggestion would be to apply it to the database.
>>
>> Em sex., 29 de jan. de 2021 às 04:09, Sean Carte 
>> escreveu:
>>
>>> Using the login.specialgroup, along with removing default read access to
>>> the collections, does restrict access to collections listed on the home
>>> page. However, anonymous access is still available to items made available
>>> by Discovery. That is, in the 'Recently Added' section, or via search, or
>>> the browse lists.
>>>
>>> Removing anonymous read access from items' bitstreams and replacing it
>>> with read access for the authenticated special group does work, but I'm
>>> going to have to repeat this process every time a new item is added. Also,
>>> the wildcard policy admin tool seems to time out when used on multiple
>>> collections, or even large collections (> ~1000), in which case the items
>>> are not modified.
>>>
>>> I suppose I could modify the UI to remove the ability to use discovery,
>>> etc., but that rather defeats the purpose of using DSpace.
>>>
>>> Is there a better approach?
>>>
>>> My goal is to have all items available to logged-in users, but nothing
>>> available to anonymous users.
>>>
>>> DSpace version:  6.3
>>> XMLUI
>>> Mirage2 theme
>>>
>>> On Wed, 27 Jan 2021 at 15:28, Sean Carte  wrote:
>>>
>>>> Thanks, José!
>>>>
>>>> On Wed, 27 Jan 2021 at 14:54, José Geraldo  wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> You can use the "login.specialgroup" and change the READ policy for
>>>>> this group.
>>>>>
>>>>>
>>>>> https://wiki.lyrasis.org/display/DSDOC5x/Authentication+Plugins#AuthenticationPlugins-ConfiguringAuthenticationbyPassword
>>>>>
>>>>> Em qua., 27 de jan. de 2021 às 05:30, Sean Carte 
>>>>> escreveu:
>>>>>
>>>>>> Is there a way to restrict access to logged-in users only, so that
>>>>>> anonymous access to collections requires a log-in?
>>>>>>
>>>>>> I understand that I can simply remove the anonymous READ
>>>>>> authorization for a collection, but then I would need to create a READ
>>>>>> authorization for a particular group, and there isn't a 'logged-in users'
>>>>>> group.
>>>>

Re: [dspace-tech] Restrict access to logged-in users only

[Sean Carte]

Thanks again, José; you've been extremely helpful.

On Fri, 29 Jan 2021 at 15:43, José Geraldo  wrote:

> Hi,
>
> Items accepted in a collection inherit the associated authorization
> policies DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ, which become READ
> policies for the item and its attachments.
>
> However, when changing the default policies for a collection, once items
> are accepted, the policies for existing items will not be changed
> automatically.
>
> Soon, a user, without logging in and in possession of the link to one of
> the items in the collection, will have access to the item and its contents.
>
> To get around this point, you will need to change the permissions of the
> items in the collection using the Policy Administration Tool to make them
> accessible only to logged-in users.
>
> For each item in a collection, there is only one READ policy configured
> for the Anonymous group.
>
> However, the tool does not have the option to edit policies, having only
> the options to add and delete policies.
>
> Therefore, it will be necessary to first delete the policies for items and
> binary files (attachments) and then create new READ policies linked to the
> special group for them.
>
> This process is done one collection at a time, if you need to apply to all
> collections, a suggestion would be to apply it to the database.
>
> Em sex., 29 de jan. de 2021 às 04:09, Sean Carte 
> escreveu:
>
>> Using the login.specialgroup, along with removing default read access to
>> the collections, does restrict access to collections listed on the home
>> page. However, anonymous access is still available to items made available
>> by Discovery. That is, in the 'Recently Added' section, or via search, or
>> the browse lists.
>>
>> Removing anonymous read access from items' bitstreams and replacing it
>> with read access for the authenticated special group does work, but I'm
>> going to have to repeat this process every time a new item is added. Also,
>> the wildcard policy admin tool seems to time out when used on multiple
>> collections, or even large collections (> ~1000), in which case the items
>> are not modified.
>>
>> I suppose I could modify the UI to remove the ability to use discovery,
>> etc., but that rather defeats the purpose of using DSpace.
>>
>> Is there a better approach?
>>
>> My goal is to have all items available to logged-in users, but nothing
>> available to anonymous users.
>>
>> DSpace version:  6.3
>> XMLUI
>> Mirage2 theme
>>
>> On Wed, 27 Jan 2021 at 15:28, Sean Carte  wrote:
>>
>>> Thanks, José!
>>>
>>> On Wed, 27 Jan 2021 at 14:54, José Geraldo  wrote:
>>>
>>>> Hi,
>>>>
>>>> You can use the "login.specialgroup" and change the READ policy for
>>>> this group.
>>>>
>>>>
>>>> https://wiki.lyrasis.org/display/DSDOC5x/Authentication+Plugins#AuthenticationPlugins-ConfiguringAuthenticationbyPassword
>>>>
>>>> Em qua., 27 de jan. de 2021 às 05:30, Sean Carte 
>>>> escreveu:
>>>>
>>>>> Is there a way to restrict access to logged-in users only, so that
>>>>> anonymous access to collections requires a log-in?
>>>>>
>>>>> I understand that I can simply remove the anonymous READ authorization
>>>>> for a collection, but then I would need to create a READ authorization for
>>>>> a particular group, and there isn't a 'logged-in users' group.
>>>>>
>>>>> I'm sure I must be missing something very obvious here, please could
>>>>> someone enlighten me.
>>>>>
>>>>> DSpace version:  6.3
>>>>>   SCM revision:  813800ce1736ec503fdcfbee4d86de836788f87c
>>>>> SCM branch:  UNKNOWN
>>>>> OS:  Linux(amd64) version 4.15.0-130-generic
>>>>>   Applications:
>>>>>  Discovery:  enabled.
>>>>>JRE:  Private Build version 1.8.0_275
>>>>>Ant version:  Apache Ant(TM) version 1.10.5 compiled on March 28
>>>>> 2019
>>>>>  Maven version:  3.3.9
>>>>>
>>>>> --
>>>>> 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.
>>

[dspace-tech] Installing dspace-angular: yarn error: no such file or directory: 'install'

[Sean Carte]

I'm trying to install dspace-angular, following the directions at:

https://wiki.lyrasis.org/display/DSPACE/DSpace+7+Preview+Release#DSpace7PreviewRelease-TryitoutusingtheDemoSite

# clone the repo
git clone https://github.com/DSpace/dspace-angular.git

# change directory to our repo
cd dspace-angular

# Checkout the "preview" release branch
git checkout preview

# install the local dependencies
yarn install

# start the server
yarn start

However, when I get to `yarn install`, yarn produces the following error:

00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'install'

I'm using Ubuntu 20.04, with yarn installed from the repos.

-- 
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/CA%2BxAuhO6nurRQWJUzGYhOpwg%3D1b_kS9-6eGkHHu-qwBzh%2Bb_nQ%40mail.gmail.com.

Re: [dspace-tech] Restrict access to logged-in users only

[Sean Carte]

Using the login.specialgroup, along with removing default read access to
the collections, does restrict access to collections listed on the home
page. However, anonymous access is still available to items made available
by Discovery. That is, in the 'Recently Added' section, or via search, or
the browse lists.

Removing anonymous read access from items' bitstreams and replacing it with
read access for the authenticated special group does work, but I'm going to
have to repeat this process every time a new item is added. Also, the
wildcard policy admin tool seems to time out when used on multiple
collections, or even large collections (> ~1000), in which case the items
are not modified.

I suppose I could modify the UI to remove the ability to use discovery,
etc., but that rather defeats the purpose of using DSpace.

Is there a better approach?

My goal is to have all items available to logged-in users, but nothing
available to anonymous users.

DSpace version:  6.3
XMLUI
Mirage2 theme

On Wed, 27 Jan 2021 at 15:28, Sean Carte  wrote:

> Thanks, José!
>
> On Wed, 27 Jan 2021 at 14:54, José Geraldo  wrote:
>
>> Hi,
>>
>> You can use the "login.specialgroup" and change the READ policy for this
>> group.
>>
>>
>> https://wiki.lyrasis.org/display/DSDOC5x/Authentication+Plugins#AuthenticationPlugins-ConfiguringAuthenticationbyPassword
>>
>> Em qua., 27 de jan. de 2021 às 05:30, Sean Carte 
>> escreveu:
>>
>>> Is there a way to restrict access to logged-in users only, so that
>>> anonymous access to collections requires a log-in?
>>>
>>> I understand that I can simply remove the anonymous READ authorization
>>> for a collection, but then I would need to create a READ authorization for
>>> a particular group, and there isn't a 'logged-in users' group.
>>>
>>> I'm sure I must be missing something very obvious here, please could
>>> someone enlighten me.
>>>
>>> DSpace version:  6.3
>>>   SCM revision:  813800ce1736ec503fdcfbee4d86de836788f87c
>>> SCM branch:  UNKNOWN
>>> OS:  Linux(amd64) version 4.15.0-130-generic
>>>   Applications:
>>>  Discovery:  enabled.
>>>JRE:  Private Build version 1.8.0_275
>>>Ant version:  Apache Ant(TM) version 1.10.5 compiled on March 28 2019
>>>  Maven version:  3.3.9
>>>
>>> --
>>> 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/CA%2BxAuhNVyzuQTjSaQCEmVq2DS7PTh8Pf_XeoYPMa-cOUvGPybA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhNVyzuQTjSaQCEmVq2DS7PTh8Pf_XeoYPMa-cOUvGPybA%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> At.te,
>>
>> José Geraldo
>>
>>

-- 
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/CA%2BxAuhOjVZegc7NWRkk8gCLL1S12TJ8huvQYykSBE6r0CJySJg%40mail.gmail.com.

Re: [dspace-tech] Updated Handle Server Init Script

[Sean Carte]

Please find the init script that we use attached.

On Thu, 28 Jan 2021 at 18:12, Ray W  wrote:

> Hi Everyone,
>
> Hope you're all safe and well, I'm reaching out to ask if anyone is
> willing to share their handle server init scripts or point me to some newer
> resources. I found this conversation that links to a wiki which
> unfortunately has not been updated.
>
> We have had some issues with our handle server and we believe the root
> cause is our startup script, hoping to see if anyone has one we can compare
> against to troubleshoot our issues.
>
> https://groups.google.com/g/dspace-tech/c/O2joqROdx5A/m/wA7fQpjzBgAJ
>
> https://wiki.duraspace.org/display/DSPACE/Handle+Service+Startup+Scripts+for+Unix+or+Linux
>
> Thank you and Take Care,
> Rachel
>
> --
> 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/4b80a2c6-2c66-42f6-a213-92049ee2687cn%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/CA%2BxAuhPBW-vNzKbadvtJ6c7T5Fgrr-jhrQLN3wW9MW-p726wXw%40mail.gmail.com.


handled
Description: Binary data

Re: [dspace-tech] Restrict access to logged-in users only

[Sean Carte]

Thanks, José!

On Wed, 27 Jan 2021 at 14:54, José Geraldo  wrote:

> Hi,
>
> You can use the "login.specialgroup" and change the READ policy for this
> group.
>
>
> https://wiki.lyrasis.org/display/DSDOC5x/Authentication+Plugins#AuthenticationPlugins-ConfiguringAuthenticationbyPassword
>
> Em qua., 27 de jan. de 2021 às 05:30, Sean Carte 
> escreveu:
>
>> Is there a way to restrict access to logged-in users only, so that
>> anonymous access to collections requires a log-in?
>>
>> I understand that I can simply remove the anonymous READ authorization
>> for a collection, but then I would need to create a READ authorization for
>> a particular group, and there isn't a 'logged-in users' group.
>>
>> I'm sure I must be missing something very obvious here, please could
>> someone enlighten me.
>>
>> DSpace version:  6.3
>>   SCM revision:  813800ce1736ec503fdcfbee4d86de836788f87c
>> SCM branch:  UNKNOWN
>> OS:  Linux(amd64) version 4.15.0-130-generic
>>   Applications:
>>  Discovery:  enabled.
>>JRE:  Private Build version 1.8.0_275
>>Ant version:  Apache Ant(TM) version 1.10.5 compiled on March 28 2019
>>  Maven version:  3.3.9
>>
>> --
>> 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/CA%2BxAuhNVyzuQTjSaQCEmVq2DS7PTh8Pf_XeoYPMa-cOUvGPybA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhNVyzuQTjSaQCEmVq2DS7PTh8Pf_XeoYPMa-cOUvGPybA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> At.te,
>
> José Geraldo
>
>

-- 
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/CA%2BxAuhPPrRvGhyxww%3DxOoSHEdBtROyO-qaF1AKUigLyXdSLbtQ%40mail.gmail.com.

[dspace-tech] Restrict access to logged-in users only

[Sean Carte]

Is there a way to restrict access to logged-in users only, so that
anonymous access to collections requires a log-in?

I understand that I can simply remove the anonymous READ authorization for
a collection, but then I would need to create a READ authorization for a
particular group, and there isn't a 'logged-in users' group.

I'm sure I must be missing something very obvious here, please could
someone enlighten me.

DSpace version:  6.3
  SCM revision:  813800ce1736ec503fdcfbee4d86de836788f87c
SCM branch:  UNKNOWN
OS:  Linux(amd64) version 4.15.0-130-generic
  Applications:
 Discovery:  enabled.
   JRE:  Private Build version 1.8.0_275
   Ant version:  Apache Ant(TM) version 1.10.5 compiled on March 28 2019
 Maven version:  3.3.9

-- 
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/CA%2BxAuhNVyzuQTjSaQCEmVq2DS7PTh8Pf_XeoYPMa-cOUvGPybA%40mail.gmail.com.

Re: [dspace-tech] Re: DSpace-Cris Site name change

[Sean Carte]

Hi Eldridge

I vaguely remember updating URI links in the past, but I'm not sure exactly
how I did it. This may help:

update metadatavalue
set text_value = regexp_replace(text_value, 'http://*my-old.url.org
*', 'https://*my-new.url.org *')
where metadata_field_id IN (select metadata_field_id from
metadatafieldregistry where element = 'identifier' and qualifier = 'uri');

After the update you need to reindex the discovery search index and the oai
index:

   - bin/dspace index-discovery -f
   - bin/dspace oai import -c

http://dspace.2283337.n4.nabble.com/cli-way-of-changing-dc-identifier-uri-for-all-items-td4687227.html

I don't know if that will have any effect on your stats links though.

On Fri, 18 Dec 2020 at 16:36, Eldridge van der Westhuizen <
dridg...@gmail.com> wrote:

> Just a correction - new link is  https://openscholar.ump.ac.za
> 
>
> On Friday, 18 December 2020 at 16:33:10 UTC+2 Eldridge van der Westhuizen
> wrote:
>
>> Good day all
>>
>> Running DSPACE-CRIS 6.3 on Ubuntu.
>>
>> Had to do a site rename from https://dspace.ump.ac.za/jspui to
>> https://openscholar.dut.ac.za
>>
>> Did all the changes in local.cfg, as well as tomcat and apache changes.
>>  Also requested a new certificate.  All working well.
>>
>> What is not working, is some of the existing article URI links, as well
>> as the statistics link.  I am attaching a screenshot with examples. Can
>> someone please assist with guidance on changing these to the correct
>> links?
>>
>> Thanks
>> Eldridge
>>
>> --
> 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/b7009130-7b60-4944-8f93-f9c5f3e6275cn%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/CA%2BxAuhNR-2XuSb2MPRi84OgoEKVp5BFtWrgphByWvX6-Ayz3AA%40mail.gmail.com.

Re: [dspace-tech] Using secure LDAP without a certificate

[Sean Carte]

Thanks, Mark. I have requested the server's certs.

On Thu, 12 Nov 2020, 17:43 Mark H. Wood,  wrote:

> /etc/ldap/ldap.conf is not involved in this, because the JVM has its
> own LDAP implementation and does not use OpenLDAP.
>
> Whenever you see errors pointing to something like "PKIX path
> building," it means that SSL/TLS is validating a certificate but
> cannot find a sequence of signer certificates that ends at a
> self-signed certificate that it has been told to trust.
>
> In Java, "told to trust" means that that certificate is in
> $JRE_HOME/jre/lib/security/cacerts, or some other suitable certificate
> database identified by the system property 'javax.net.ssl.trustStore'.
> Here's some documentation as a starting point:
>
>
> https://docs.oracle.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide.html#CustomizingStores
>
> Also this article might help:
>
>
> https://stackoverflow.com/questions/6908948/java-sun-security-provider-certpath-suncertpathbuilderexception-unable-to-find
>
> Here are my own notes on how to install my own CA certificate in the
> default trust store:
>
>   'cd' to $JRE_HOME/jre/lib/security
>
>   Make a copy of 'cacerts' for error recovery.
>
>   keytool -import \
>   -alias my-root \
>   -file /some/path/to/my-root.pem \
>   -keystore cacerts
>
> On Thu, Nov 12, 2020 at 01:09:35PM +0200, Sean Carte wrote:
> > Thanks for the response, Alan.
> >
> > It seems the problem for me is that our ldap (AD) server is using a PKI
> > certificate, which appears to be self-signed. I really don't understand
> how
> > that works. But from what I've read, that's what's causing the problem.
>
> Yes, that certificate won't be in your JVM's trust store unless you
> add it.
>
> > On Thu, 12 Nov 2020 at 11:23, Alan Orth  wrote:
> >
> > > Hi Sean,
> > >
> > > I'm using LDAPS on both DSpace 5.8 and 6.3. For DSpace 5 I have the
> > > following in my sitename.properties:
> > >
> > > ldap.provider_url = ldaps://blahblah.org:636/
> > >
> > > For DSpace 6 I have this in my local.cfg:
> > >
> > > authentication-ldap.provider_url = ldaps://blahblah.org:636/
> > >
> > > I have not configured any STARTTLS parameters in DSpace or the system's
> > > ldap.conf. We are using Ubuntu 18.04.
> > >
> > > Regards,
> > >
> > > On Thu, Nov 12, 2020 at 9:34 AM Sean Carte 
> wrote:
> > >
> > >> I'm trying to configure DSpace-CRIS 5.10 and DSpace 6.3 to use ldaps,
> but
> > >> get this error in the log:
> > >>
> > >> 2020-11-11 15:05:03,464 WARN
> org.dspace.authenticate.LDAPAuthentication
> > >> @
> anonymous:session_id=F261C03287498D5AEE67FFE7F53CBCAF:ip_addr=10.0.36.134:
> ldap_authentication:type=failed_auth
> > >> javax.naming.CommunicationException\colon; simple bind failed\colon;
> > >> \colon;636 [Root exception is
> > >> javax.net.ssl.SSLHandshakeException\colon; PKIX path building
> failed\colon;
> > >> sun.security.provider.certpath.SunCertPathBuilderException\colon;
> unable to
> > >> find valid certification path to requested target]
> > >>
> > >> LDAP authentication is working without SSL. All I've changed in the
> > >> configuration is ldap -> ldaps in the provider_url property.
> > >>
> > >> On the DSpace 6.3 server I've also tried:
> > >> authentication-ldap.starttls=true
> > >> while leaving the scheme at ldap
> > >>
> > >> That results in the following error:
> > >>
> > >> 2020-11-12 09:06:32,112 WARN
> org.dspace.authenticate.LDAPAuthentication
> > >> @
> anonymous:session_id=0BD2A90CE7458F21149D8505D76D7E78:ip_addr=10.0.36.134:
> ldap_authentication:type=failed_auth
> > >> javax.net.ssl.SSLHandshakeException\colon; PKIX path building
> failed\colon;
> > >> sun.security.provider.certpath.SunCertPathBuilderException\colon;
> unable to
> > >> find valid certification path to requested target
> > >>
> > >> I also tried using ldapsearch and found that that fails on ldaps with
> the
> > >> error 'TLS: peer cert untrusted or revoked (0x142)' unless I add the
> > >> following line to /etc/ldap/ldap.conf:
> > >>
> > >> TLS_REQCERT NEVER
> > >>
> > >> That setting in ldap.conf doesn't seem to have any effect on DSpace;
> is
> > >> there a way of telling DSpace to not expect a server certificate?

Re: [dspace-tech] Using secure LDAP without a certificate

[Sean Carte]

Thanks for the response, Alan.

It seems the problem for me is that our ldap (AD) server is using a PKI
certificate, which appears to be self-signed. I really don't understand how
that works. But from what I've read, that's what's causing the problem.

On Thu, 12 Nov 2020 at 11:23, Alan Orth  wrote:

> Hi Sean,
>
> I'm using LDAPS on both DSpace 5.8 and 6.3. For DSpace 5 I have the
> following in my sitename.properties:
>
> ldap.provider_url = ldaps://blahblah.org:636/
>
> For DSpace 6 I have this in my local.cfg:
>
> authentication-ldap.provider_url = ldaps://blahblah.org:636/
>
> I have not configured any STARTTLS parameters in DSpace or the system's
> ldap.conf. We are using Ubuntu 18.04.
>
> Regards,
>
> On Thu, Nov 12, 2020 at 9:34 AM Sean Carte  wrote:
>
>> I'm trying to configure DSpace-CRIS 5.10 and DSpace 6.3 to use ldaps, but
>> get this error in the log:
>>
>> 2020-11-11 15:05:03,464 WARN  org.dspace.authenticate.LDAPAuthentication
>> @ 
>> anonymous:session_id=F261C03287498D5AEE67FFE7F53CBCAF:ip_addr=10.0.36.134:ldap_authentication:type=failed_auth
>> javax.naming.CommunicationException\colon; simple bind failed\colon;
>> \colon;636 [Root exception is
>> javax.net.ssl.SSLHandshakeException\colon; PKIX path building failed\colon;
>> sun.security.provider.certpath.SunCertPathBuilderException\colon; unable to
>> find valid certification path to requested target]
>>
>> LDAP authentication is working without SSL. All I've changed in the
>> configuration is ldap -> ldaps in the provider_url property.
>>
>> On the DSpace 6.3 server I've also tried:
>> authentication-ldap.starttls=true
>> while leaving the scheme at ldap
>>
>> That results in the following error:
>>
>> 2020-11-12 09:06:32,112 WARN  org.dspace.authenticate.LDAPAuthentication
>> @ 
>> anonymous:session_id=0BD2A90CE7458F21149D8505D76D7E78:ip_addr=10.0.36.134:ldap_authentication:type=failed_auth
>> javax.net.ssl.SSLHandshakeException\colon; PKIX path building failed\colon;
>> sun.security.provider.certpath.SunCertPathBuilderException\colon; unable to
>> find valid certification path to requested target
>>
>> I also tried using ldapsearch and found that that fails on ldaps with the
>> error 'TLS: peer cert untrusted or revoked (0x142)' unless I add the
>> following line to /etc/ldap/ldap.conf:
>>
>> TLS_REQCERT NEVER
>>
>> That setting in ldap.conf doesn't seem to have any effect on DSpace; is
>> there a way of telling DSpace to not expect a server certificate? Or is
>> there a better way to get secure LDAP working?
>>
>> --
>> 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/CA%2BxAuhNZ4oB76KB57%2B4xrWybbOYqDyiytVUjvNTq%2B8%2BoWJWENg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhNZ4oB76KB57%2B4xrWybbOYqDyiytVUjvNTq%2B8%2BoWJWENg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> Alan Orth
> alan.o...@gmail.com
> https://picturingjordan.com
> https://englishbulgaria.net
> https://mjanja.ch
>

-- 
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/CA%2BxAuhPBrrL1tcJWJomE7xTgLRR_W0Fbsr3WkBywVe7-xOzP-Q%40mail.gmail.com.

[dspace-tech] Using secure LDAP without a certificate

[Sean Carte]

I'm trying to configure DSpace-CRIS 5.10 and DSpace 6.3 to use ldaps, but
get this error in the log:

2020-11-11 15:05:03,464 WARN  org.dspace.authenticate.LDAPAuthentication @
anonymous:session_id=F261C03287498D5AEE67FFE7F53CBCAF:ip_addr=10.0.36.134:ldap_authentication:type=failed_auth
javax.naming.CommunicationException\colon; simple bind failed\colon;
\colon;636 [Root exception is
javax.net.ssl.SSLHandshakeException\colon; PKIX path building failed\colon;
sun.security.provider.certpath.SunCertPathBuilderException\colon; unable to
find valid certification path to requested target]

LDAP authentication is working without SSL. All I've changed in the
configuration is ldap -> ldaps in the provider_url property.

On the DSpace 6.3 server I've also tried:
authentication-ldap.starttls=true
while leaving the scheme at ldap

That results in the following error:

2020-11-12 09:06:32,112 WARN  org.dspace.authenticate.LDAPAuthentication @
anonymous:session_id=0BD2A90CE7458F21149D8505D76D7E78:ip_addr=10.0.36.134:ldap_authentication:type=failed_auth
javax.net.ssl.SSLHandshakeException\colon; PKIX path building failed\colon;
sun.security.provider.certpath.SunCertPathBuilderException\colon; unable to
find valid certification path to requested target

I also tried using ldapsearch and found that that fails on ldaps with the
error 'TLS: peer cert untrusted or revoked (0x142)' unless I add the
following line to /etc/ldap/ldap.conf:

TLS_REQCERT NEVER

That setting in ldap.conf doesn't seem to have any effect on DSpace; is
there a way of telling DSpace to not expect a server certificate? Or is
there a better way to get secure LDAP working?

-- 
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/CA%2BxAuhNZ4oB76KB57%2B4xrWybbOYqDyiytVUjvNTq%2B8%2BoWJWENg%40mail.gmail.com.

Re: [dspace-tech] SQL Injection Vulnerability

[Sean Carte]

Good points; thanks, Tim and Emilio. I wasn't about to *report* a
vulnerability, I was really just asking for advice on how to address this.
(I could have phrased my question better.)

As you suggest, *if* IT or the auditors do supply anything concrete, I will
take it up directly with 4Science.

On Wed, 21 Oct 2020 at 16:15, Tim Donohue  wrote:

> All,
>
> Per our DSpace Software Support policy, we have a recommended way to
> report security issues privately to the developer team:
> https://wiki.lyrasis.org/display/DSPACE/DSpace+Software+Support+Policy
>
> To analyze a potential security issue, we *require*​ some sort of proof
> or example way to exploit the vulnerability.  At this time, there are no
> known SQL injection vulnerabilities related to DSpace.
>
> That said, the above support policy does *NOT*​ apply to DSpace-CRIS,
> which is a third-party product built/supported/maintained by 4Science
> <https://www.4science.it/en/>.  You'd need to contact 4Science directly
> regarding any security issues/reports with DSpace-CRIS.
>
> Thanks,
>
> Tim
> --
> *From:* dspace-tech@googlegroups.com  on
> behalf of emilio lorenzo 
> *Sent:* Wednesday, October 21, 2020 2:32 AM
> *To:* dspace-tech@googlegroups.com 
> *Subject:* Re: [dspace-tech] SQL Injection Vulnerability
>
>
> in any case, I think that information about vulnerabilities must be keep
> off the public lists,...  the "group" has mechanisms to deal with these
> issues.
> it is only an idea...
> BEST
>
> Emilio
>
>
> On 20/10/2020 10:10, Sean Carte wrote:
>
> I'm running DSpace-CRIS 5.10 and have received a message from our IT dept
> alerting me to an SQL injection vulnerability on our repository.
>
> It seems the auditors were using HighBond, but they haven't given me any
> details as to how they assessed this vulnerability.
>
> I'm supposed to do something about it, but I don't know what.
>
> Is there a known vulnerability in DSpace-CRIS 5.10?
>
> /dspacecris-dut/bin/dspace version
> DSpace version:  CRIS-5.10.0-SNAPSHOT
>   SCM revision:  8390fec2945050541427ef1249dbbbd56b1ccdc4
> SCM branch:  fix-sword
> OS:  Linux(amd64) version 4.4.0-190-generic
>  Discovery:  enabled.
>JRE:  Private Build version 1.8.0_265
>Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20 2018
>  Maven version:  3.3.9
>DSpace home:  /dspacecris-dut
> --
> 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/CA%2BxAuhPWr8AO5xqkkTE1SbzXK%3D6xuswSS%2BmmfBPoj9OH3s0w4g%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhPWr8AO5xqkkTE1SbzXK%3D6xuswSS%2BmmfBPoj9OH3s0w4g%40mail.gmail.com?utm_medium=email_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/81bc6792-7978-a3b2-1bf2-82a239fc245c%40arvo.es
> <https://groups.google.com/d/msgid/dspace-tech/81bc6792-7978-a3b2-1bf2-82a239fc245c%40arvo.es?utm_medium=email_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/DM5PR2201MB1148B556D17188670CF03876ED1C0%40DM5PR2201MB1148.namprd22.prod.outlook.com
> <https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB1148B556D17188670CF03876ED1C0%40DM5PR2201MB1148.namprd22.prod.outlook.com?utm_medium=email_source=footer>
> .
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/poli

Re: [dspace-tech] Re: SQL Injection Vulnerability

[Sean Carte]

Thanks, David. That is helpful; I was thinking along similar lines, but
didn't know if I was in the right. I will revert to our IT dept.

On Wed, 21 Oct 2020 at 02:12,  wrote:

> Without more information from your IT dept and the auditor, you would have
> to guess at this one at any field that allows user input.
>
>
>
> Although someone more familiar with DSpace CRIS might have more
> information.
>
>
>
> Another thing you can try is looking at issue trackers. I don’t see
> anything at the DSpace CRIS tracker
> https://github.com/4Science/DSpace/issues, and I don’t see anything
> obvious when searching the DSpace issue tracker:
> https://jira.lyrasis.org/projects/DS/issues.
>
>
>
> David Cook
>
> Software Engineer
>
> Prosentient Systems
>
> 72/330 Wattle St
>
> Ultimo, NSW 2007
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> *From:* dspace-tech@googlegroups.com  *On
> Behalf Of *Sean Carte
> *Sent:* Wednesday, 21 October 2020 5:38 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Re: SQL Injection Vulnerability
>
>
>
> I just did a search for
>
>
>
> 'Bobby; DROP TABLE "bitstream";'
>
>
>
> That didn't seem to do anything too catastrophic, apart from finding
> results.
>
>
>
> On Tue, 20 Oct 2020, 10:10 Sean Carte,  wrote:
>
> I'm running DSpace-CRIS 5.10 and have received a message from our IT dept
> alerting me to an SQL injection vulnerability on our repository.
>
>
>
> It seems the auditors were using HighBond, but they haven't given me any
> details as to how they assessed this vulnerability.
>
>
>
> I'm supposed to do something about it, but I don't know what.
>
>
>
> Is there a known vulnerability in DSpace-CRIS 5.10?
>
>
>
> /dspacecris-dut/bin/dspace version
> DSpace version:  CRIS-5.10.0-SNAPSHOT
>   SCM revision:  8390fec2945050541427ef1249dbbbd56b1ccdc4
> SCM branch:  fix-sword
> OS:  Linux(amd64) version 4.4.0-190-generic
>
>  Discovery:  enabled.
>JRE:  Private Build version 1.8.0_265
>Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20 2018
>  Maven version:  3.3.9
>DSpace home:  /dspacecris-dut
>
> --
> 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/CA%2BxAuhPQ9-Bq4agJASMvekOho7rgtokLk4C3DQgLq1Jr%3Dy1O%3DA%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhPQ9-Bq4agJASMvekOho7rgtokLk4C3DQgLq1Jr%3Dy1O%3DA%40mail.gmail.com?utm_medium=email_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/CA%2BxAuhNZJZpMie-AHcqLh2cJAX1mxoQeJybJvnrce9VsdEgjFg%40mail.gmail.com.

[dspace-tech] Re: SQL Injection Vulnerability

[Sean Carte]

I just did a search for

'Bobby; DROP TABLE "bitstream";'

That didn't seem to do anything too catastrophic, apart from finding
results.

On Tue, 20 Oct 2020, 10:10 Sean Carte,  wrote:

> I'm running DSpace-CRIS 5.10 and have received a message from our IT dept
> alerting me to an SQL injection vulnerability on our repository.
>
> It seems the auditors were using HighBond, but they haven't given me any
> details as to how they assessed this vulnerability.
>
> I'm supposed to do something about it, but I don't know what.
>
> Is there a known vulnerability in DSpace-CRIS 5.10?
>
> /dspacecris-dut/bin/dspace version
> DSpace version:  CRIS-5.10.0-SNAPSHOT
>   SCM revision:  8390fec2945050541427ef1249dbbbd56b1ccdc4
> SCM branch:  fix-sword
> OS:  Linux(amd64) version 4.4.0-190-generic
>  Discovery:  enabled.
>JRE:  Private Build version 1.8.0_265
>Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20 2018
>  Maven version:  3.3.9
>DSpace home:  /dspacecris-dut
>

-- 
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/CA%2BxAuhPQ9-Bq4agJASMvekOho7rgtokLk4C3DQgLq1Jr%3Dy1O%3DA%40mail.gmail.com.

[dspace-tech] SQL Injection Vulnerability

[Sean Carte]

I'm running DSpace-CRIS 5.10 and have received a message from our IT dept
alerting me to an SQL injection vulnerability on our repository.

It seems the auditors were using HighBond, but they haven't given me any
details as to how they assessed this vulnerability.

I'm supposed to do something about it, but I don't know what.

Is there a known vulnerability in DSpace-CRIS 5.10?

/dspacecris-dut/bin/dspace version
DSpace version:  CRIS-5.10.0-SNAPSHOT
  SCM revision:  8390fec2945050541427ef1249dbbbd56b1ccdc4
SCM branch:  fix-sword
OS:  Linux(amd64) version 4.4.0-190-generic
 Discovery:  enabled.
   JRE:  Private Build version 1.8.0_265
   Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20 2018
 Maven version:  3.3.9
   DSpace home:  /dspacecris-dut

-- 
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/CA%2BxAuhPWr8AO5xqkkTE1SbzXK%3D6xuswSS%2BmmfBPoj9OH3s0w4g%40mail.gmail.com.

[dspace-tech] DSpace-CRIS 5.10 Update JQuery

[Sean Carte]

What would be involved in updating jquery on DSpace-CRIS 5.10 to something
more recent?

I ask because our network security has identified vulnerabilities in
jquery-1.11 currently in use in DSpace-CRIS 5.10.

-- 
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/CA%2BxAuhMM%2BjzDuHQzwcHkOGsbnrz7tgFJUx8_qM4am4mY811B2A%40mail.gmail.com.

Re: [dspace-tech] How do I do mvn and ant a second time ?

[Sean Carte]

Do as the documentation instructs: run mvn package from the dspace-source
directory.

The ant update command should copy everything from your build directory to
your tomcat directory. No need for manual copying.

On Fri, 6 Mar 2020 at 11:01, Ashim Kapoor  wrote:

> Dear Sean,
>
> I have a query.
>
> On Tue, 3 Mar 2020 at 11:57, Sean Carte  wrote:
>
>> This may help:
>> https://wiki.lyrasis.org/display/DSDOC6x/Upgrading+DSpace
>>
>> cd [dspace-source]/dspace/
>> mvn -U clean package
>>
>
> On this page :- https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace
> cd [dspace-source]
> mvn package
>
> Query : What is the right directory for running mvn? [dspace-source] or
> [dspace-source]/dspace/ ?
>
>
> cd [dspace-source]/dspace/target/dspace-installer
>> ant update
>>
>
> After do the ant update above, am I supposed to do this:-
>
> cp -R [dspace]/webapps/* [tomcat]/webapps*
>
> Please clarify.
>
>>
>> On Mon, 2 Mar 2020 at 18:54, Ashim Kapoor 
>> wrote:
>>
>>> Dear All,
>>>
>>> How can I clean up and run mvn and ant after I have run it once ?
>>>
>>> Suppose in my local.cfg I have to modify dspace.dir or the ip address in
>>> dspace.hostname. How do I re-run mvn and ant after modifying one or both of
>>> them ?
>>>
>>> Many thanks,
>>> 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 view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/CAGEJAoEeAFTytTf0wTYhN6ZkR5XAwY0Pq%3D0TaGnAVJW_%3D6AYJw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/dspace-tech/CAGEJAoEeAFTytTf0wTYhN6ZkR5XAwY0Pq%3D0TaGnAVJW_%3D6AYJw%40mail.gmail.com?utm_medium=email_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/CA%2BxAuhN6kL3uPP1UrSa1UKQFPDxzt_ZN4432uksYEMwSkXawzw%40mail.gmail.com.

Re: [dspace-tech] ORCID Authorities: Updating author profiles to their ORCID equivalents

[Sean Carte]

My thoughts exactly. Thanks, Miika.

On Tue, 3 Mar 2020 at 19:10, Nurminen, Miika 
wrote:

> On 3.3.2020 15:51, Sean Carte wrote:
> > It seems that in this repository all the authors have been entered
> > using dc.creator rather than contributor.author.
> >
> > I suppose I'm going to have to find a way to move all the authors into
> > contributor.author fields before any of this can work.
>
>
> Hi Sean,
>
> This is probably not a recommended way compared to e.g. CSV-files or
> REST updates but if modifying the database directly is an option (e.g.
> during a service break with backups in place just in case), the fastest
> way to accomplish this would be a SQL update, e.g.
>
> UPDATE metadatavalue SET metadata_field_id=[dc.contributor.author]
> WHERE metadata_field_id=[dc.creator id];
>
> where [...]s are numeric ids retrievable from the metadata registry
> (e.g. in our database dc.contributor has id 1 and dc.contributor.author
> has id 3).
>
>
> Good luck,
> Miika Nurminen
>


--

-- 
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/CA%2BxAuhMeuhdobgbazm5LFFbORcwK3b2cnVV6r6vGi8CZ_ZcDKQ%40mail.gmail.com.

Re: [dspace-tech] ORCID Authorities: Updating author profiles to their ORCID equivalents

[Sean Carte]

Thanks for the input, Emilio.

It seems that in this repository all the authors have been entered using
dc.creator rather than contributor.author.

I suppose I'm going to have to find a way to move all the authors into
contributor.author fields before any of this can work.

On Tue, 3 Mar 2020 at 13:44, emilio lorenzo  wrote:

> hi Sean
>
> first guess is that the two entries ("the browse index then lists the
> author's name twice")  belongs to entries with different confidence levels
> (200 vs 500 or so...) . The Index separates entries if confidence values
> are not the same (there are substantial difference between values)  if one
> of  them do not reach enough  "confidence"
>
> Second guess (I prefer this)...   the authors in you current index has a
> given "internal" authority key and Orcid validated authors enters into the
> repository with "orcid id" as the key..  So, different keys, different
> entries
>
> Some time ago we developed for EUI´s Cadmus repository a method for *joining
> *entries belonging to different validation sources.  There was a
> communication to OR2019 explaining this.
>
> Best luck
>
> Emilio
>
>
> El 03/03/2020 a las 9:11, Sean Carte escribió:
>
> Is there a way to link existing authors with their ORCID equivalents?
>
> In a DSpace 6.3 repository, using Mirage2 xmlui with several thousand
> authors, we are considering enabling ORCID authority control, but won't
> this lead to the creation of duplicate authors?
>
> I have an author with 31 publications on the repository, but when I create
> a new submission and lookup the author's name, I can find it on ORCID, but
> it says 'items in this repository: 0'.
>
> If I use the ORCID id to submit the item, the browse index then lists the
> author's name twice, once with 31 publications, and once with 1 publication.
>
> Even if I rebuild the discovery index: dspace index-discovery -fb, the two
> apparently identical author's names continue to be listed separately.
>
> If I submit a new item using the name from the ORCID index, a subsequent
> search looking up that author's name still finds the name in the ORCID
> index (italicised) with 'items in this repository: 0', but now there is
> also a non-italicised name with a link to view items. Following that link
> takes me to the recently deposited item, but no others. So it looks like
> I've now got three versions of the author: the original, the ORCID id, and
> the newly created one.
>
> I'm not sure what I'm doing wrong, but surely this can't be right.
> --
>
> --
> 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/CA%2BxAuhP_mnGm0Y7Wax10n6yPusN6efOvT_AomhDX9YtGkB4r3g%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhP_mnGm0Y7Wax10n6yPusN6efOvT_AomhDX9YtGkB4r3g%40mail.gmail.com?utm_medium=email_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/CA%2BxAuhN%2B_RCstrvaAawVZC7-kV6tYPj7md6UzkEPJFZhNzQ48w%40mail.gmail.com.

[dspace-tech] ORCID Authorities: Updating author profiles to their ORCID equivalents

[Sean Carte]

Is there a way to link existing authors with their ORCID equivalents?

In a DSpace 6.3 repository, using Mirage2 xmlui with several thousand
authors, we are considering enabling ORCID authority control, but won't
this lead to the creation of duplicate authors?

I have an author with 31 publications on the repository, but when I create
a new submission and lookup the author's name, I can find it on ORCID, but
it says 'items in this repository: 0'.

If I use the ORCID id to submit the item, the browse index then lists the
author's name twice, once with 31 publications, and once with 1 publication.

Even if I rebuild the discovery index: dspace index-discovery -fb, the two
apparently identical author's names continue to be listed separately.

If I submit a new item using the name from the ORCID index, a subsequent
search looking up that author's name still finds the name in the ORCID
index (italicised) with 'items in this repository: 0', but now there is
also a non-italicised name with a link to view items. Following that link
takes me to the recently deposited item, but no others. So it looks like
I've now got three versions of the author: the original, the ORCID id, and
the newly created one.

I'm not sure what I'm doing wrong, but surely this can't be right.
--

-- 
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/CA%2BxAuhP_mnGm0Y7Wax10n6yPusN6efOvT_AomhDX9YtGkB4r3g%40mail.gmail.com.

Re: [dspace-tech] How do I do mvn and ant a second time ?

[Sean Carte]

This may help:
https://wiki.lyrasis.org/display/DSDOC6x/Upgrading+DSpace

cd [dspace-source]/dspace/
mvn -U clean package

cd [dspace-source]/dspace/target/dspace-installer
ant update


On Mon, 2 Mar 2020 at 18:54, Ashim Kapoor  wrote:

> Dear All,
>
> How can I clean up and run mvn and ant after I have run it once ?
>
> Suppose in my local.cfg I have to modify dspace.dir or the ip address in
> dspace.hostname. How do I re-run mvn and ant after modifying one or both of
> them ?
>
> Many thanks,
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CAGEJAoEeAFTytTf0wTYhN6ZkR5XAwY0Pq%3D0TaGnAVJW_%3D6AYJw%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/CA%2BxAuhMGiuYQet_1y%3DFxggOv83JEm4d7o1vh6rd0%2BtUAKFThYA%40mail.gmail.com.

Re: [dspace-tech] Permissions of the [dspace] directory

[Sean Carte]

I think that's correct.

On Mon, 2 Mar 2020 at 18:50, Ashim Kapoor  wrote:

> Hi again,
>
> I meant :-
>
> The second constraint is that [2] needs to be run by a user who is able to
> read the [dspace-source] and write to the [dspace] directory.
>
> On Mon, 2 Mar 2020 at 22:18, Ashim Kapoor 
> wrote:
>
>> Hello,
>>
>> now I think I get it.
>>
>> I need to run
>> 1. mvn
>> and
>> 2. ant fresh_install
>>
>> These may be run by 2 different users.
>> The first constraint here is that [1] has to be run by a user who has rwx
>> permission over [dspace-source] directory.
>> The second constraint is that [2] needs to be able to read the
>> [dspace-source] and write to the [dspace] directory.
>>
>> Please correct me if I am mistaken.
>>
>> Thank you,
>> Ashim
>>
>> On Thu, 27 Feb 2020 at 16:53, Sean Carte  wrote:
>>
>>> That is correct: your user (dspace or whatever you choose to run mvn,
>>> etc.), needs rwx permission for the dspace-src directory.
>>>
>>> I think you may have misunderstood what Mark was telling you: the
>>> *installer* (ant) needs to be able to read the dspace-src and write to
>>> the dspace directories:
>>>
>>> The build directory ([dspace-source]) can be owned by any account you
>>> choose.  You just need a way to run the installer so that it can read
>>> the [dspace-source] directory tree and write the [dspace] directory
>>> tree.
>>>
>>>
>>> On Thu, 27 Feb 2020 at 13:13, Ashim Kapoor 
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I am mistaken.
>>>>
>>>> To build the directory [dspace] I need to do :-
>>>> ant fresh_install
>>>>
>>>> Till the time I do this the [dspace] folder will be empty.
>>>>
>>>> but coming to the query that we need only read permission for
>>>> [dspace-source].
>>>>
>>>> When we do mvn package, it will build a target directory inside
>>>> dspace-source folder. That is why it needs BOTH read and write permissions
>>>> for the [dspace-source].
>>>>
>>>> Please correct me if I am wrong.
>>>>
>>>> Best,
>>>> Ashim
>>>>
>>>> On Thu, 27 Feb 2020 at 15:50, Ashim Kapoor 
>>>> wrote:
>>>>
>>>>> Hello Again,
>>>>>
>>>>> before I do mvn package, I gave dspace.dir = /home/dspace in my
>>>>> local.cfg. It is ignoring this and building the script in
>>>>> [dspace-source]/dspace.
>>>>>
>>>>> Perhaps this is the reason it needs write permissions for
>>>>> [dspace-source]
>>>>>
>>>>> Can you please help me ?
>>>>> Thank you,
>>>>> Ashim
>>>>>
>>>>>
>>>>>
>>>>> On Thu, 27 Feb 2020 at 15:22, Ashim Kapoor 
>>>>> wrote:
>>>>>
>>>>>> Dear Mark,
>>>>>>
>>>>>> I think the build directory [dspace-source] also needs write
>>>>>> permissions by the account which is used while doing "mvn package"
>>>>>>
>>>>>> I get this error when I try building by non root user who does not
>>>>>> have write permission for [dspace-source]:
>>>>>>
>>>>>> [ERROR] Failed to execute goal
>>>>>> org.apache.maven.plugins:maven-resources-plugin:2.7:resources
>>>>>> (default-resources) on project additions: Cannot create resource output
>>>>>> directory:
>>>>>> /home/ashim/dspace-6.3-release/dspace/modules/additions/target/classes ->
>>>>>> [Help 1]
>>>>>>
>>>>>> Am I missing something?
>>>>>>
>>>>>> Best Regards,
>>>>>> Ashim
>>>>>>
>>>>>> On Thu, 27 Feb 2020 at 15:01, Ashim Kapoor 
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, 26 Feb 2020 at 20:12, Mark H. Wood 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> On Wed, Feb 26, 2020 at 10:30:57AM +0530, Ashim Kapoor wrote:
>>>>>>>> > I am reading this
>>>>>>>> > <https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace>
>>>&g

Re: [dspace-tech] Internal System Error for JSPUI

[Sean Carte]

Please let us know what is in your /dspace/log/dspace.log.[date] file at
the time when the error occurred.

On Thu, 27 Feb 2020 at 13:59, Ashim Kapoor 
wrote:

> Dear All,
>
> When I do http://192.100.30.xxx/jspui I get :-
> Internal System Error
>
> The system has experienced an internal error. Please try to do what you
> were doing again, and if the problem persists, please contact us so we can
> fix the problem.
>
> Earlier:-
> chown -R tomcat:tomcat [dspace] made jspui work. But now I get the above 
> error. Can someone point me in the right direction ?
>
> Thank you,
>
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CAGEJAoFJQB0-fME8ZKaLB0kd%2BVynmBYDBnOaN9KoyA46vFYtmw%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/CA%2BxAuhM4st1yiEDeKa7F0g3FfJ9Or24URPjvUkG%3D5u51zK%3DTTA%40mail.gmail.com.

Re: [dspace-tech] Query about solr configuration

[Sean Carte]

Somebody, please correct me if I'm wrong, but I don't think there's any
practical difference as far as Tomcat and solr are concerned. However, if
you change your IP address at some stage, that's one other setting that
you're going to have to remember to change.

On Thu, 27 Feb 2020 at 13:20, Ashim Kapoor 
wrote:

> Hello,
>
> Thank you for your email. What exactly is the difference between setting
> it as localhost vs 192.100.30.xxx ? Can you please elaborate?
>
> Best,
> Ashim
>
> On Thu, 27 Feb 2020 at 16:46, Sean Carte  wrote:
>
>> As your tomcat is on the same server as solr, localhost is fine. Leave it
>> as is.
>>
>> On Thu, 27 Feb 2020 at 12:01, Ashim Kapoor 
>> wrote:
>>
>>> Dear All,
>>>
>>> Here is an excerpt from local.cfg
>>>
>>> # Solr server/webapp.
>>> # DSpace uses Solr for all search/browse capability (and for usage
>>> statistics by default).
>>> # The included 'solr' webapp MUST be deployed to Tomcat for DSpace to
>>> function.
>>> # Usually it will be available via port 8080 and the 'solr' context
>>> path. But,
>>> # But, you may need to modify this if you are running DSpace on a custom
>>> port, etc.
>>>
>>> *solr.server = http://localhost:8080/solr <http://localhost:8080/solr>*
>>>
>>> My IP address for the app is 192.100.30.xxx
>>>
>>> Should I modify and make :-
>>> *solr.server = http://192.100.30.xxx:8080/solr
>>> <http://192.100.30.xxx:8080/solr>*
>>>
>>> Please clarify.
>>>
>>> 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 view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/CAGEJAoGBU%3D4GR-n6Oh426gkkWQa_y1u6xvQOxHmgPR0WrRf2Cw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/dspace-tech/CAGEJAoGBU%3D4GR-n6Oh426gkkWQa_y1u6xvQOxHmgPR0WrRf2Cw%40mail.gmail.com?utm_medium=email_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/CA%2BxAuhPETTH8fziVcWv67aeuyezmgBO8w_s1e9yVqvvoMagUig%40mail.gmail.com.

Re: [dspace-tech] Permissions of the [dspace] directory

[Sean Carte]

That is correct: your user (dspace or whatever you choose to run mvn,
etc.), needs rwx permission for the dspace-src directory.

I think you may have misunderstood what Mark was telling you: the
*installer* (ant) needs to be able to read the dspace-src and write to the
dspace directories:

The build directory ([dspace-source]) can be owned by any account you
choose.  You just need a way to run the installer so that it can read
the [dspace-source] directory tree and write the [dspace] directory
tree.


On Thu, 27 Feb 2020 at 13:13, Ashim Kapoor 
wrote:

> Hi,
>
> I am mistaken.
>
> To build the directory [dspace] I need to do :-
> ant fresh_install
>
> Till the time I do this the [dspace] folder will be empty.
>
> but coming to the query that we need only read permission for
> [dspace-source].
>
> When we do mvn package, it will build a target directory inside
> dspace-source folder. That is why it needs BOTH read and write permissions
> for the [dspace-source].
>
> Please correct me if I am wrong.
>
> Best,
> Ashim
>
> On Thu, 27 Feb 2020 at 15:50, Ashim Kapoor 
> wrote:
>
>> Hello Again,
>>
>> before I do mvn package, I gave dspace.dir = /home/dspace in my
>> local.cfg. It is ignoring this and building the script in
>> [dspace-source]/dspace.
>>
>> Perhaps this is the reason it needs write permissions for [dspace-source]
>>
>> Can you please help me ?
>> Thank you,
>> Ashim
>>
>>
>>
>> On Thu, 27 Feb 2020 at 15:22, Ashim Kapoor 
>> wrote:
>>
>>> Dear Mark,
>>>
>>> I think the build directory [dspace-source] also needs write permissions
>>> by the account which is used while doing "mvn package"
>>>
>>> I get this error when I try building by non root user who does not have
>>> write permission for [dspace-source]:
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-resources-plugin:2.7:resources
>>> (default-resources) on project additions: Cannot create resource output
>>> directory:
>>> /home/ashim/dspace-6.3-release/dspace/modules/additions/target/classes ->
>>> [Help 1]
>>>
>>> Am I missing something?
>>>
>>> Best Regards,
>>> Ashim
>>>
>>> On Thu, 27 Feb 2020 at 15:01, Ashim Kapoor 
>>> wrote:
>>>


 On Wed, 26 Feb 2020 at 20:12, Mark H. Wood 
 wrote:

> On Wed, Feb 26, 2020 at 10:30:57AM +0530, Ashim Kapoor wrote:
> > I am reading this
> > 
> >
> > At one place it says :
> > # Change [dspace] and all subfolders to be owned by "tomcat"
> > chown -R tomcat:tomcat [dspace]
> >
> > At another place it says :
> > mkdir [dspace]
> > chown dspace [dspace]
>
> Thank you for pointing this out.  I thought we had removed all of that
> confusion.
>
> > I think that FIRST we have to do :-
> >
> > 1. chown dspace [dpspace]
> > 2. Then run maven and ant
> >
> > When I am building the webapp using maven and ant the user dspace
> needs
> > ownership over the [dspace] directory.
> >
> > Once it is built, THEN we should do :-
> >
> > chown -R tomcat:tomcat [dspace]
> >
> > So that tomcat has permissions over dspace directory.
> >
> > Do I understand this correctly?
>
> I think that would work.  But, read on.
>
> > Query: Suppose after running maven and ant, I do:-
> >
> > cp -R [dspace]/webapps/* [tomcat]/webapps*
> >
> > Then does tomcat still need to have permissions over [dpsace] ? In
> other
> > words, do I still need to do:-
> >
> > chown -R tomcat:tomcat [dspace]
>
> Tomcat needs read access to all of the files in [dspace], and write
> access to many of them.  The easiest way to do this is to have them
> all owned by the account which runs Tomcat, with rwx access for
> owner.  The documentation calls that account 'tomcat', but on your
> system Tomcat may have been installed to use an account with a
> different name.  Whatever that account is called, it should own the
> files that make up the installed instance of DSpace ([dspace]).
>
> The build directory ([dspace-source]) can be owned by any account you
> choose.  You just need a way to run the installer so that it can read
> the [dspace-source] directory tree and write the [dspace] directory
> tree.
>

 Many thanks for this info. Now I am more clear as to what permissions
 to use.


> There is no need for a separate 'dspace' account.  We need to finish
> removing that from the documentation.  DSpace does not know or care
> about OS accounts.  Tomcat has to care because it is what needs the
> permissions -- DSpace runs inside Tomcat and uses Tomcat's
> permissions.
>
> --
> Mark H. Wood
> Lead Technology Analyst
>
> University Library
> Indiana University - Purdue University Indianapolis
> 755 W. Michigan Street
> Indianapolis, IN 46202
> 317-274-0749
> 

Re: [dspace-tech] Query about solr configuration

[Sean Carte]

As your tomcat is on the same server as solr, localhost is fine. Leave it
as is.

On Thu, 27 Feb 2020 at 12:01, Ashim Kapoor 
wrote:

> Dear All,
>
> Here is an excerpt from local.cfg
>
> # Solr server/webapp.
> # DSpace uses Solr for all search/browse capability (and for usage
> statistics by default).
> # The included 'solr' webapp MUST be deployed to Tomcat for DSpace to
> function.
> # Usually it will be available via port 8080 and the 'solr' context path.
> But,
> # But, you may need to modify this if you are running DSpace on a custom
> port, etc.
>
> *solr.server = http://localhost:8080/solr *
>
> My IP address for the app is 192.100.30.xxx
>
> Should I modify and make :-
> *solr.server = http://192.100.30.xxx:8080/solr
> *
>
> Please clarify.
>
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CAGEJAoGBU%3D4GR-n6Oh426gkkWQa_y1u6xvQOxHmgPR0WrRf2Cw%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/CA%2BxAuhNSXOoFfdNhPgpAuhHo_4bMRb6Li1jm8H0v0hqdd%2B2kSw%40mail.gmail.com.

Re: [dspace-tech] Difficulty setting up dspace 6.3

[Sean Carte]

I don't know about your maven-enforcer-plugin error, but the first error is
a permissions problem. As root:
 chown -R dspace:dspace /home/dspace/dspace-6.3-release/

On Wed, 26 Feb 2020 at 13:43, Ashim Kapoor 
wrote:

> Dear All,
>
> I am following instructions on this page:-
>
> https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace
>
> When I do mvn package as root I don't get the following error.
>
> However when I do mvn package as unix user dspace I get the following
> error:-
>
>
> [INFO] Reactor Summary for DSpace Parent Project 6.3:
> [INFO]
> [INFO] DSpace Parent Project .. SUCCESS [
>  1.209 s]
> [INFO] DSpace Addon Modules ... SUCCESS [
>  0.038 s]
> [INFO] DSpace Kernel :: Additions and Local Customizations  SUCCESS [
>  6.209 s]
> [INFO] DSpace XML-UI (Manakin) :: Local Customizations  SUCCESS [
> 15.203 s]
> [INFO] DSpace JSP-UI :: Local Customizations .. SUCCESS [
>  7.210 s]
> [INFO] DSpace RDF :: Local Customizations . SUCCESS [
>  6.657 s]
> [INFO] DSpace REST :: Local Customizations  SUCCESS [
>  8.845 s]
> [INFO] DSpace SWORD :: Local Customizations ... SUCCESS [
>  6.799 s]
> [INFO] DSpace SWORD v2 :: Local Customizations  SUCCESS [
>  6.757 s]
> [INFO] DSpace SOLR :: Local Customizations  FAILURE [
>  3.155 s]
> [INFO] DSpace OAI-PMH :: Local Customizations . SKIPPED
> [INFO] DSpace Assembly and Configuration .. SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time:  01:02 min
> [INFO] Finished at: 2020-02-26T17:04:45+05:30
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-war-plugin:2.6:war (default-war) on project
> solr: Failed to copy file for artifact
> [org.dspace:dspace-solr:jar:classes:6.3:compile]:
> /home/dspace/dspace-6.3-release/dspace/modules/solr/target/solr-6.3/WEB-INF/lib/dspace-solr-6.3-classes.jar
> (Permission denied) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :solr
> $
>
> Also in BOTH cases I get this warning :-
>
> $ mvn package
> [INFO] Scanning for projects...
> [WARNING] The project org.dspace:dspace-parent:pom:6.3 uses prerequisites
> which is only intended for maven-plugin projects but not for non
> maven-plugin projects. For such purposes you should use the
> maven-enforcer-plugin. See
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
>
>
> Can someone please help me ?
>
> Thank you,
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CAGEJAoF7Gc%2B2Rv8hZA380rvEhHMBZ_0RPgusi-NKg2se--aNzg%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/CA%2BxAuhMueaZhSBVANQG9SkDfBeyW4hTNKZPB7qLnTaBeD204tQ%40mail.gmail.com.

Re: [dspace-tech] SOLR error: too many boolean clauses

[Sean Carte]

Thank you, Claudia!

Disabling the Access Rights Awareness feature does appear to resolve the
issue.

I did try increasing the maxBooleanClauses setting first, but it looks like
this may get set elsewhere, so I found all the solrconfig.xml and increased
it in all of them. That also resolves the issue.

On Mon, 17 Feb 2020 at 17:44, Claudia Jürgen 
wrote:

> Hello Sean,
>
> this might be related to the Access Rights Awareness
> see
>
> https://wiki.lyrasis.org/display/DSPACE/TechnicalFaq#TechnicalFAQ-I'mgetting%22SolrException:BadRequest%22followedbyalongqueryora%22tooManyClauses%22Exception
>
> Hope this helps
>
> Claudia Jürgen
>
>
> Am 17.02.2020 um 13:34 schrieb Sean Carte:
> > I have a dspace 6.3 instance running on Ubuntu 18.04.3. When a user who
> > belongs to two groups that are authorised to add to and edit all
> > collections, a very long error is generated, ending with:
> >
> > ...
> > OR l9d9b96b2-ae23-40ea-9e98-46a8537ac4b5 OR
> > lf94b27dc-2c22-476c-a012-72f36b50d521 OR
> > lfd7afb4f-8a09-4412-8044-2acbe584fa76)': too many boolean clauses
> >  at
> >
> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:552)
> >  at
> >
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
> >  at
> >
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
> >  at
> >
> org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:91)
> >  at
> > org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:310)
> >  at
> > org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:1610)
> >  ... 364 more
> >
> > I've attached the solr.log containing the full error.
> >
> > Removing the user from either of the groups resolves the problem. Also,
> if
> > the user is an administrator the problem does not occur.
> >
> > The problem occurs irrespective of the UI.
> >
> > I downloaded a fresh copy of DSpace and updated the existing installation
> > with it, but that didn't help. I deleted the /dspace directory and did a
> > fresh installation, then restored the database; the problem persists.
> >
> > But, I copied the database to a laptop (running the same versions of all
> > software) and the problem went away.
> >
> > If the problem doesn't exist in the database, where could it be? Does
> > anybody have any ideas?
> >
> > DSpace version:  6.3
> >SCM revision:  813800ce1736ec503fdcfbee4d86de836788f87c
> >  SCM branch:  UNKNOWN
> >  OS:  Linux(amd64) version 4.15.0-74-generic
> >   Discovery:  enabled.
> > JRE:  Private Build version 1.8.0_242
> > Ant version:  Apache Ant(TM) version 1.10.5 compiled on March 28 2019
> >   Maven version:  3.3.9
> > DSpace home:  /dspace
> > Tomcat 8
> > PostgreSQL 10
> >
> > /etc/default/tomcat8: JAVA_OPTS="-Djava.awt.headless=true -Xmx8192m
> > -Xms4096m -XX:+UseConcMarkSweepGC -Dfile.encoding=UTF-8
> > -XX:MaxPermSize=512m"
> > --
> >
>
> --
> Claudia Juergen
> Eldorado
>
> Technische Universität Dortmund
> Universitätsbibliothek
> Vogelpothsweg 76
> 44227 Dortmund
>
> Tel.: +49 231-755 40 43
> Fax: +49 231-755 40 32
> claudia.juer...@tu-dortmund.de
> www.ub.tu-dortmund.de
>
>
> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie
> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für
> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender
> und vernichten Sie diese Mail. Vielen Dank.
> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines
> solchen Schriftstücks per Telefax erfolgen.
>
> Important note: The information included in this e-mail is confidential.
> It is solely intended for the recipient. If you are not the intended
> recipient of this e-mail please contact the sender and delete this message.
> Thank you. Without prejudice of e-mail correspondence, our statements are
> only legally binding when they are made in the conventional written form
> (with personal signature) or when such documents are sent by fax.
>
> --
> 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
> &quo

Re: [dspace-tech] Custom logout page/redirect

[Sean Carte]

What version of DSpace are you using? I was seeing something similar to
what you describe on 5.x (using Firefox), but it does appear to be resolved
in 6.3.

On Tue, 28 Jan 2020 at 15:55, Hawk, Patrick  wrote:

> Any suggestions?
>
> On Wed, Jan 15, 2020 at 9:29 AM Hawk, Patrick  wrote:
>
>> The redirect isn't working in Chrome of Firefox but MS Edge redirects to
>> the main page after log out.
>>
>> On Mon, Jan 6, 2020 at 4:20 PM Patrick Hawk  wrote:
>>
>>> Currently, if I log out of dspace I get a blank log out page.  I want to
>>> redirect to the main page instead.  How is this accomplished?
>>>
>>> --
>>> 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/af3a4c73-cb0b-4f81-8c06-0c5fcc4854c2%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>>
>> 
>>
>> Patrick Hawk
>>
>> Computer and Technology Specialist
>>
>> Miami University Libraries
>>
>> 314 King Library
>>
>> 151 S. Campus Ave.
>> 
>>
>> Oxford, OH 45056
>> 
>>
>> O: 513-529-6122 | haw...@miamioh.edu
>>
>
>
> --
>
> 
>
> Patrick Hawk
>
> Computer and Technology Specialist
>
> Miami University Libraries
>
> 314 King Library
>
> 151 S. Campus Ave.
> 
>
> Oxford, OH 45056
> 
>
> O: 513-529-6122 | haw...@miamioh.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/CAH_HnmVBC6FuEZ%2BfC0Gb%3DSRdSJF1-on9731zeT3%3DWDZD%3D%2B9Wug%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/CA%2BxAuhPYjgPCY%2Bu3UW5X%3DuSF7k2288qyeLsU%2BLFkac1w8oKkNg%40mail.gmail.com.

Re: [dspace-tech] deleting repeated form entries during submission

[Sean Carte]

I'm using DSpace-CRIS 5.10 and clicking 'Add More' adds a single addition
field. I don't see any delete button unless the field is populated, then
the 'Remove Entry' button is displayed; clicking it does delete the field.
Also, if I click a different 'Add More' button and the field has not been
populated, it is removed.

   
 dc
 contributor
 author
 true
 Authors
 onebox
 Enter the names of the authors of this item in the form
Surname, Firstname [i.e. Smith, Josh or Smith, J].
 
   



On Fri, 17 Jan 2020 at 15:58, Marc  wrote:

> Dear List,
>
> During item submission it is possible to have repeated fields e.g.
> dc.contributing.author. Buttons are provided to delete and add entries. At
> the moment clicking the add button, adds two new blank entries and clicking
> the delete button does nothing. we are using DSpace CRIS 5.8 and the
> browser we are using is Firefox latest build. Is this a known issue and if
> so is there a work around?
>
> 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/9cca51bf-132c-4dab-bdc1-3df258e51b5f%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/CA%2BxAuhPkh4ZbHNvcyCqA_eQq3JQ%3DeyERpcOGQOhdA%3DEvs3_7jQ%40mail.gmail.com.

Re: [dspace-tech] Marking robots by user agent with `stats-util -m` is not implemented

[Sean Carte]

Thanks, Alan!

Total number of bot hits purged: 575004

One thing I found curious is that I first ran it with -pno -d, then -pyes
and got a different result each time:

dspace@ir:/home/dspace$ scripts/check-spider-hits.sh -u
http://localhost:8080/solr -f /dspacecris-dut/config/spiders/agents/example
-pno -d
(DEBUG) Using spiders pattern file:
/dspacecris-dut/config/spiders/agents/example
(DEBUG) Checking for hits from spider: AllenTrack
(DEBUG) Checking for hits from spider: Arachmo
(DEBUG) Checking for hits from spider: ContentSmartz
(DEBUG) Checking for hits from spider: DSurf
(DEBUG) Checking for hits from spider: EmailSiphon
(DEBUG) Checking for hits from spider: EmailWolf
(DEBUG) Checking for hits from spider: GetRight
(DEBUG) Checking for hits from spider: Googlebot
Found 325498 hits from Googlebot in statistics
(DEBUG) Checking for hits from spider: HTTrack
Found 1366 hits from HTTrack in statistics
(DEBUG) Checking for hits from spider: LOCKSS
(DEBUG) Checking for hits from spider: MSNBot
(DEBUG) Checking for hits from spider: Milbot
(DEBUG) Checking for hits from spider: MuscatFerre
(DEBUG) Checking for hits from spider: NABOT
(DEBUG) Checking for hits from spider: NaverBot
(DEBUG) Checking for hits from spider: OurBrowser
(DEBUG) Checking for hits from spider: Readpaper
(DEBUG) Checking for hits from spider: Strider
Found 1 hits from Strider in statistics
(DEBUG) Checking for hits from spider: Teoma
Found 2 hits from Teoma in statistics
(DEBUG) Checking for hits from spider: Wanadoo
Found 7 hits from Wanadoo in statistics
(DEBUG) Checking for hits from spider: WebCloner
(DEBUG) Checking for hits from spider: WebCopier
(DEBUG) Checking for hits from spider: WebReaper
(DEBUG) Checking for hits from spider: WebStripper
(DEBUG) Checking for hits from spider: WebZIP
(DEBUG) Checking for hits from spider: Webinator
(DEBUG) Checking for hits from spider: Webmetrics
(DEBUG) Checking for hits from spider: Wget
Found 170 hits from Wget in statistics
(DEBUG) Checking for hits from spider: alexa
Found 238 hits from alexa in statistics
(DEBUG) Checking for hits from spider: almaden
(DEBUG) Checking for hits from spider: appie
(DEBUG) Checking for hits from spider: architext
(DEBUG) Checking for hits from spider: arks
Found 18 hits from arks in statistics
(DEBUG) Checking for hits from spider: asterias
(DEBUG) Checking for hits from spider: atomz
(DEBUG) Checking for hits from spider: autoemailspider
(DEBUG) Checking for hits from spider: awbot
(DEBUG) Checking for hits from spider: baiduspider
(DEBUG) Checking for hits from spider: bbot
(DEBUG) Checking for hits from spider: biadu
(DEBUG) Checking for hits from spider: biglotron
(DEBUG) Checking for hits from spider: bjaaland
(DEBUG) Checking for hits from spider: bloglines
(DEBUG) Checking for hits from spider: blogpulse
(DEBUG) Checking for hits from spider: bot
Found 520514 hits from bot in statistics
(DEBUG) Checking for hits from spider: bspider
Found 72 hits from bspider in statistics
(DEBUG) Checking for hits from spider: bwh3_user_agent
(DEBUG) Checking for hits from spider: celestial
(DEBUG) Checking for hits from spider: cfnetwork|checkbot
(DEBUG) Solr query returned HTTP 400, skipping cfnetwork|checkbot.
(DEBUG) Checking for hits from spider: combine
(DEBUG) Checking for hits from spider: contentmatch
(DEBUG) Checking for hits from spider: core
(DEBUG) Checking for hits from spider: crawl
Found 15205 hits from crawl in statistics
(DEBUG) Checking for hits from spider: crawler
Found 15191 hits from crawler in statistics
(DEBUG) Checking for hits from spider: cursor
(DEBUG) Checking for hits from spider: custo
Found 4 hits from custo in statistics
(DEBUG) Checking for hits from spider: daumoa
(DEBUG) Checking for hits from spider: docomo
(DEBUG) Checking for hits from spider: dtSearchSpider
(DEBUG) Checking for hits from spider: dumbot
(DEBUG) Checking for hits from spider: easydl
(DEBUG) Checking for hits from spider: exabot
Found 133 hits from exabot in statistics
(DEBUG) Checking for hits from spider: fast-webcrawler
(DEBUG) Checking for hits from spider: favorg
(DEBUG) Checking for hits from spider: feedburner
(DEBUG) Checking for hits from spider: ferret
(DEBUG) Checking for hits from spider: findlinks
Found 10626 hits from findlinks in statistics
(DEBUG) Checking for hits from spider: gaisbot
(DEBUG) Checking for hits from spider: geturl
(DEBUG) Checking for hits from spider: gigabot
(DEBUG) Checking for hits from spider: girafabot
(DEBUG) Checking for hits from spider: gnodspider
(DEBUG) Checking for hits from spider: google
Found 327642 hits from google in statistics
(DEBUG) Checking for hits from spider: grub
(DEBUG) Checking for hits from spider: gulliver
(DEBUG) Checking for hits from spider: harvest
(DEBUG) Checking for hits from spider: heritrix
Found 765 hits from heritrix in statistics
(DEBUG) Checking for hits from spider: hl_ftien_spider
(DEBUG) Checking for hits from spider: holmes
(DEBUG) Checking for hits from spider: htdig

Re: [dspace-tech] Re: jsp.display-item.citation.google.tooltip

[Sean Carte]

I think you need to edit /dspace/config/news-top.html

On Tue, 29 Oct 2019 at 15:52, Gerald Okeke  wrote:

> [image: Customise Dpace Homepage.png]
> Greetings,
>
> I kindly request on how to customize the homepage of the Dspace software.
> I wish to change the characters in the part circled in the picture
> uploaded.. Kindly assist me please. I have searched everywhere on the
> dspace folder, but was unsuccessful
>
> On Tuesday, 29 October 2019 07:45:23 UTC+1, Sean Carte wrote:
>>
>> Using DSpace-CRIS 5.10, when hovering over the Google Scholar Check link,
>> I get '???jsp.display-item.citation.google.tooltip???'. Clearly I need to
>> set a message for that key, but:
>>
>> what should the message be, and
>> where do I set it.
>>
>> I notice the dspace-cris demo site <https://dspace-cris.4science.it/>
>> has a similar problem.
>>
>> [image: Selection_025.png]
>>
>> --
>>
>> --
> 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/517d8e09-d383-4497-9c51-26df0ec40def%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/517d8e09-d383-4497-9c51-26df0ec40def%40googlegroups.com?utm_medium=email_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/CA%2BxAuhMFfer3K9Z-FvfSOCCo%2BDxzR_6SjLcmamsxLGN2evcowA%40mail.gmail.com.

Re: [dspace-tech] jsp.display-item.citation.google.tooltip

[Sean Carte]

Thanks, Pham. I tried copying the Messages.properties file to
/dspace/webapps/jspui/WEB-INF/classes/, but that didn't seem to make any
difference.

However, I found the file in my my dspace-src directory:
dspace-api/src/main/resources/Messages.properties; so it looks like I'll
need to modify that file, including the line:

jsp.display-item.citation.google.tooltip = Search Google Scholar

then rebuild dspace.

On Tue, 29 Oct 2019 at 12:11, Pham Quang Quyen 
wrote:

> You download this file and copy to /dspace/webapps/jspui/WEB-INF/classes,
> then you restart your tomcat.
> Good luck
> Sincerely,
> Pham Quang Quyen (librarian of VietNam).
>
> On Tue, Oct 29, 2019 at 1:45 PM Sean Carte  wrote:
>
>> Using DSpace-CRIS 5.10, when hovering over the Google Scholar Check link,
>> I get '???jsp.display-item.citation.google.tooltip???'. Clearly I need to
>> set a message for that key, but:
>>
>> what should the message be, and
>> where do I set it.
>>
>> I notice the dspace-cris demo site <https://dspace-cris.4science.it/>
>> has a similar problem.
>>
>> [image: Selection_025.png]
>>
>> --
>>
>> --
>> 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/CA%2BxAuhPZ1cXETL0eEZ-gRqxPrtXqsbhWuQr7eu2biH4xpdCNhg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhPZ1cXETL0eEZ-gRqxPrtXqsbhWuQr7eu2biH4xpdCNhg%40mail.gmail.com?utm_medium=email_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/CA%2BxAuhOhO8OQnHFjTHzPbKpCBZOCFzvPzS0hFHdh-hvGZkv-%3DQ%40mail.gmail.com.

[dspace-tech] jsp.display-item.citation.google.tooltip

[Sean Carte]

Using DSpace-CRIS 5.10, when hovering over the Google Scholar Check link, I
get '???jsp.display-item.citation.google.tooltip???'. Clearly I need to set
a message for that key, but:

what should the message be, and
where do I set it.

I notice the dspace-cris demo site  has a
similar problem.

[image: Selection_025.png]

--

-- 
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/CA%2BxAuhPZ1cXETL0eEZ-gRqxPrtXqsbhWuQr7eu2biH4xpdCNhg%40mail.gmail.com.

Re: [dspace-tech] What is a crosswalk ?

[Sean Carte]

A mapping between different metadata standards.

https://www.sciencedirect.com/topics/computer-science/crosswalk

On Thu, 19 Sep 2019 at 17:23, Ashim Kapoor 
wrote:

> Dear All,
>
> I am reading this :-
> https://wiki.duraspace.org/display/DSDOC6x/AIP+Backup+and+Restore
>
> I have a query. What is a crosswalk ?
>
> Thank you,
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CAGEJAoG%2BFc1%3DPtowEtUhDa%2BeRQMuFEguTwwmBGTseydwGv2A8Q%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/CA%2BxAuhOvd-pB_EO-Zvon%3DJnz%3D45EoeivjQHH%3D41NOfQ01xRVcw%40mail.gmail.com.

Re: [dspace-tech] Additional browse indexes in DSpace-CRIS

[Sean Carte]

Thank you again, Andrea. Very helpful! I'll add more examples to the
documentation as I figure stuff out.

On Thu, 19 Sep 2019 at 15:06, Bollini Andrea 
wrote:

> Thanks Sean, help on the documentation is very welcome!
>
> > - modify the fields displayed in the Discover section of the Research
> > Outputs page; and
>
> if you mean how the publication are listed in the most viewed, most
> download, etc. box this is defined here
>
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/spring/cris/cris-processor.xml#L82
>
> 
> where the dspaceitemsLayoutView is defined in
>
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/spring/api/global-list-layout.xml#L15
>
> If instead you are asking about the discovery configuration applied in
> the section it comes from the key used for the section
>
>
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/spring/cris/cris-processor.xml#L67
>
> 
>
> that must match a discovery configuration
>
>
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/spring/api/discovery.xml#L134
>
> - modify the contents of the navbar.
>
>
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/modules/cris.cfg#L5
> navbar.cris-entities
> <https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/modules/cris.cfg#L5navbar.cris-entities>
> =
> publications,researcherprofiles,orgunits,fundings
>
> this is the list of the explore sections, the name must match the
> configuration in the cris-processor and discovery as by above links
>
> Best,
> Andrea
>
>
>
>
> On Thu, 2019-09-19 at 07:54 +0200, Sean Carte wrote:
> > Thanks, Andrea. That is very helpful. Following your advice, I was
> > able to add buttons (facets?) to the Browse panel in the Communities
> > and Collections pages, as well as add links to the Browse section in
> > the Research Outputs page.
> >
> > I will add these examples to the documentation.
> >
> > What I still don't know how to do is:
> > - modify the fields displayed in the Discover section of the Research
> > Outputs page; and
> > - modify the contents of the navbar.
> >
> > On Wed, 18 Sep 2019 at 00:51, Bollini Andrea <
> > andrea.boll...@4science.it> wrote:
> > > Hi Sean,
> > > you need to map the configured browse to an entity type so that it
> > > will
> > > appear in the relevant area of the website.
> > >
> > > To add a browse to the community or collection home page see
> > >
> > >
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/dspace.cfg#L2363
> > >
> > > to add the browse to a specific explore section, for instance
> > >
> > >
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/spring/cris/cris-processor.xml#L72
> > > are the browses related to the publications section
> > >
> > >
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/spring/cris/cris-processor.xml#L67
> > >
> > > please be sure also to limit the sort options available for the
> > > browse
> > > index to the relevant ones, see
> > >
> > >
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/dspace.cfg#L2360
> > >
> > > If the above information will help, I would appreciate if you can
> > > improve the documentation here
> > > https://wiki.duraspace.org/pages/viewpage.action?pageId=78153687
> > > Best,
> > > Andrea
> > >
> > >
> > > On Tue, 2019-09-17 at 14:57 +0200, Sean Carte wrote:
> > > > In the XML UI I can add additional browse indexes by adding
> > > > search.index.n and webui.browse.index.n fields, e.g., to add a
> > > > 'level' index for a defined field dc.description.level, I would
> > > add
> > > > the following to dspace.cfg:
> > > >
> > > > search.index.15 = level:dc.description.level
> > > > webui.browse.index.7 = level:metadata:dc.description.level:text
> > > >
> > > > and add the appropriate description to messages.xml:
> > > >
> > > >  > > >
> > > key="xmlui.ArtifactBrowser.ConfigurableBrowse.level.column_heading"
> > > >Q
> > > > ualification Level
> > > >  > > >
> > > key="xmlui.ArtifactBrowser.ConfigurableBrowse.title.metadata.level"
> > > >B
> > > 

Re: [dspace-tech] Additional browse indexes in DSpace-CRIS

[Sean Carte]

Thanks, Andrea. That is very helpful. Following your advice, I was able to
add buttons (facets?) to the Browse panel in the Communities and
Collections pages, as well as add links to the Browse section in the
Research Outputs page.

I will add these examples to the documentation.

What I still don't know how to do is:
- modify the fields displayed in the Discover section of the Research
Outputs page; and
- modify the contents of the navbar.

On Wed, 18 Sep 2019 at 00:51, Bollini Andrea 
wrote:

> Hi Sean,
> you need to map the configured browse to an entity type so that it will
> appear in the relevant area of the website.
>
> To add a browse to the community or collection home page see
>
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/dspace.cfg#L2363
>
> to add the browse to a specific explore section, for instance
>
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/spring/cris/cris-processor.xml#L72
> are the browses related to the publications section
>
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/spring/cris/cris-processor.xml#L67
>
> please be sure also to limit the sort options available for the browse
> index to the relevant ones, see
>
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/dspace.cfg#L2360
>
> If the above information will help, I would appreciate if you can
> improve the documentation here
> https://wiki.duraspace.org/pages/viewpage.action?pageId=78153687
> Best,
> Andrea
>
>
> On Tue, 2019-09-17 at 14:57 +0200, Sean Carte wrote:
> > In the XML UI I can add additional browse indexes by adding
> > search.index.n and webui.browse.index.n fields, e.g., to add a
> > 'level' index for a defined field dc.description.level, I would add
> > the following to dspace.cfg:
> >
> > search.index.15 = level:dc.description.level
> > webui.browse.index.7 = level:metadata:dc.description.level:text
> >
> > and add the appropriate description to messages.xml:
> >
> >  > key="xmlui.ArtifactBrowser.ConfigurableBrowse.level.column_heading">Q
> > ualification Level
> >  > key="xmlui.ArtifactBrowser.ConfigurableBrowse.title.metadata.level">B
> > rowsing {0} by Qualification Level {1}
> >  > key="xmlui.ArtifactBrowser.ConfigurableBrowse.trail.metadata.level">B
> > rowsing {0} by Qualification level {1}
> >  > key="xmlui.ArtifactBrowser.Navigation.browse_level">Qualification
> > Level
> >
> > Then, bin/dspace index-discovery -b -f
> >
> > And the new items appear in the Browse list.
> >
> > Similarly for the JSP UI, except I need to edit  dspace-
> > api/src/main/resources/Messages.properties and rebuild the webapp:
> >
> > browse.menu.level = Qualification Level
> > browse.type.metadata.level = Qualification Level
> >
> > According to
> > https://wiki.duraspace.org/pages/viewpage.action?pageId=78153687 , it
> > looks like I should follow a similar process for DSpace-CRIS:
> >
> >   webui.browse.index. = :: > name>[:DESC]
> >
> > should create the indexes, but I can't find any way to display or use
> > them. I have added the fields to Messages.properties and reindexed. I
> > expected the new items to appear in the 'Discover' box, but that
> > remains unchanged.
> >
> > I would like to add items to the navbar, but that's starting to seem
> > like a distant dream.
> >
> > What am I doing wrong?
> >
> > DSpace version:  CRIS-5.10.0-SNAPSHOT
> >  Discovery:  enabled.
> >JRE:  Private Build version 1.8.0_222
> >Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20
> > 2018
> >  Maven version:  3.3.9
> > --
> >
> > --
> > 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/CA%2BxAuhO5guoi6c_7hoD%2BAJfUD3kp3_NyFbeZrsbDvqXMJgMGUQ%40mail.gmail.com
> > .
> >
>
> --
> Questo messaggio e' stato analizzato da Libra ESVA ed e' risultato non
> infetto.
> This message was scanned by Libra ESVA and is believed to be clean.
>
>

--

-- 
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/CA%2BxAuhP-YT7%2BpjnCgVe7omH3SBwBTYf6DLSqVeJuW9hxV9UZrg%40mail.gmail.com.

[dspace-tech] Additional browse indexes in DSpace-CRIS

[Sean Carte]

In the XML UI I can add additional browse indexes by adding search.index.n
and webui.browse.index.n fields, e.g., to add a 'level' index for a defined
field dc.description.level, I would add the following to dspace.cfg:

search.index.15 = level:dc.description.level
webui.browse.index.7 = level:metadata:dc.description.level:text

and add the appropriate description to messages.xml:

Qualification
Level
Browsing
{0} by Qualification Level {1}
Browsing
{0} by Qualification level {1}
Qualification
Level

Then, bin/dspace index-discovery -b -f

And the new items appear in the Browse list.

Similarly for the JSP UI, except I need to edit
dspace-api/src/main/resources/Messages.properties and rebuild the webapp:

browse.menu.level = Qualification Level
browse.type.metadata.level = Qualification Level

According to
https://wiki.duraspace.org/pages/viewpage.action?pageId=78153687 , it looks
like I should follow a similar process for DSpace-CRIS:

  webui.browse.index. = ::[:DESC]

should create the indexes, but I can't find any way to display or use them.
I have added the fields to Messages.properties and reindexed. I expected
the new items to appear in the 'Discover' box, but that remains unchanged.

I would like to add items to the navbar, but that's starting to seem like a
distant dream.

What am I doing wrong?

DSpace version:  CRIS-5.10.0-SNAPSHOT
 Discovery:  enabled.
   JRE:  Private Build version 1.8.0_222
   Ant version:  Apache Ant(TM) version 1.9.6 compiled on July 20 2018
 Maven version:  3.3.9
--

-- 
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/CA%2BxAuhO5guoi6c_7hoD%2BAJfUD3kp3_NyFbeZrsbDvqXMJgMGUQ%40mail.gmail.com.

[dspace-tech] Error viewing submissions page with Mirage2

[Sean Carte]

One particular user has a problem viewing the submissions page, using the
XML UI on DSpace 6.3. Other users don't have the same problem, and this
user can view the submissions page using the JSP UI.

DSpace version:  6.3
SCM revision:  ${buildNumber}
SCM branch:  UNKNOWN_BRANCH
OS:  Linux(amd64) version 4.15.0-47-generic
Discovery:  enabled.
JRE:  Oracle Corporation version 1.8.0_191
Ant version:  Apache Ant(TM) version 1.10.3 compiled on July 19 2018
Maven version:  3.5.2
DSpace home:  /dspace

I've tried other XML themes, with the same result.

Any ideas as to how I can get this user to view the submissions page using
Mirage2?

Nothing appears in the dspace log, but the floowing stacktrace is displayed
in the browser:

Java stacktrace: java.lang.NullPointerException
at
org.dspace.app.xmlui.aspect.submission.Submissions.addPreviousSubmissions(Submissions.java:394)
at
org.dspace.app.xmlui.aspect.submission.Submissions.addBody(Submissions.java:147)
at
org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:234)
at
java.base/jdk.internal.reflect.GeneratedMethodAccessor164.invoke(Unknown
Source)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
at com.sun.proxy.$Proxy217.startElement(Unknown Source)
at
org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87)
at
org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94)
at
org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251)
at
java.base/jdk.internal.reflect.GeneratedMethodAccessor164.invoke(Unknown
Source)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
at com.sun.proxy.$Proxy218.startElement(Unknown Source)
at
org.apache.cocoon.environment.internal.EnvironmentChanger.startElement(EnvironmentStack.java:140)
at
org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87)
at
org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94)
at
org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251)
at
java.base/jdk.internal.reflect.GeneratedMethodAccessor164.invoke(Unknown
Source)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
at com.sun.proxy.$Proxy218.startElement(Unknown Source)
at
org.apache.cocoon.environment.internal.EnvironmentChanger.startElement(EnvironmentStack.java:140)
at
org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87)
at
org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94)
at
org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251)
at
java.base/jdk.internal.reflect.GeneratedMethodAccessor164.invoke(Unknown
Source)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
at com.sun.proxy.$Proxy218.startElement(Unknown Source)
at
org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94)
at
org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251)
at
java.base/jdk.internal.reflect.GeneratedMethodAccessor164.invoke(Unknown
Source)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
at com.sun.proxy.$Proxy218.startElement(Unknown Source)
at
org.apache.cocoon.environment.internal.EnvironmentChanger.startElement(EnvironmentStack.java:140)
at
org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87)
at
org.apache.cocoon.components.sax.AbstractXMLByteStreamInterpreter.parse(AbstractXMLByteStreamInterpreter.java:117)
at
org.apache.cocoon.components.sax.XMLByteStreamInterpreter.deserialize(XMLByteStreamInterpreter.java:44)
at

Re: [dspace-tech] Custom Item Submission

[Sean Carte]

Thanks, Claudia.

On Wed, 20 Mar 2019 at 15:37, Claudia Jürgen 
wrote:

> Hi Sean,
>
> sure there is an option visibility (workflow or submit) see
> https://wiki.duraspace.org/display/DSDOC5x/Submission+User+Interface
>
> So you can not distinct by group directly but between submission and
> workflow.
>
> Hope this helps
>
> Claudia Jürgen
>
> Am 20.03.2019 um 14:32 schrieb Sean Carte:
> > I need to configure a custom item submission for a specific group of
> users
> > (submitters). After they submit, I need another group to be able to add
> > metadata.
> >
> > I initially thought I could create a special input form and submission
> > process, but of course, these are tied to a collection, not a user group.
> > So even metadata editors see the same fields and steps as the submitters.
> >
> > Is there a way to have submitters see different fields to metadata
> editors?
> >
> > DSpace-CRIS 5.10
> > --
> >
>
> --
> Claudia Juergen
> Eldorado
>
> Technische Universität Dortmund
> Universitätsbibliothek
> Vogelpothsweg 76
> 44227 Dortmund
>
> Tel.: +49 231-755 40 43
> Fax: +49 231-755 40 32
> claudia.juer...@tu-dortmund.de
> www.ub.tu-dortmund.de
>
> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie
> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für
> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender
> und vernichten Sie diese Mail. Vielen Dank.
> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines
> solchen Schriftstücks per Telefax erfolgen.
>
> Important note: The information included in this e-mail is confidential.
> It is solely intended for the recipient. If you are not the intended
> recipient of this e-mail please contact the sender and delete this message.
> Thank you. Without prejudice of e-mail correspondence, our statements are
> only legally binding when they are made in the conventional written form
> (with personal signature) or when such documents are sent by fax.
>
> --
> 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] Custom Item Submission

[Sean Carte]

I need to configure a custom item submission for a specific group of users
(submitters). After they submit, I need another group to be able to add
metadata.

I initially thought I could create a special input form and submission
process, but of course, these are tied to a collection, not a user group.
So even metadata editors see the same fields and steps as the submitters.

Is there a way to have submitters see different fields to metadata editors?

DSpace-CRIS 5.10
--

-- 
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: Swordv2 Deposit in DSpace-CRIS 5.10

[Sean Carte]

ting to https://test.dspace-cris.4science.it. This results
in a 405: HTTP method GET is not supported by this URL.

curl -v -i --data-binary "@Downloads/Singh_2009.pdf" -H
"Content-Disposition:attachment; filename=Singh_2009.pdf" -H
"Content-Type:application/pdf" -H "Packaging:
http://purl.org/net/sword/package/Binary; -u
dspacecris-u...@mailinator.com:dspacecris-user
-X POST https://test.dspace-cris.4science.it/handle/123456789/6
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying 34.249.45.66...
* Connected to test.dspace-cris.4science.it (34.249.45.66) port 443 (#0)
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 597 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
*  server certificate verification OK
*  server certificate status verification SKIPPED
*  common name: test.dspace-cris.4science.it (matched)
*  server certificate expiration date OK
*  server certificate activation date OK
*  certificate public key: RSA
*  certificate version: #3
*  subject: CN=test.dspace-cris.4science.it
*  start date: Sat, 09 Feb 2019 11:11:01 GMT
*  expire date: Fri, 10 May 2019 11:11:01 GMT
*  issuer: C=US,O=Let's Encrypt,CN=Let's Encrypt Authority X3
*  compression: NULL
* ALPN, server accepted to use http/1.1
* Server auth using Basic with user 'dspacecris-u...@mailinator.com'
> POST /handle/123456789/6 HTTP/1.1
> Host: test.dspace-cris.4science.it
> Authorization: Basic
ZHNwYWNlY3Jpcy11c2VyQG1haWxpbmF0b3IuY29tOmRzcGFjZWNyaXMtdXNlcg==
> User-Agent: curl/7.47.0
> Accept: */*
> Content-Disposition:attachment; filename=Singh_2009.pdf
> Content-Type:application/pdf
> Packaging:http://purl.org/net/sword/package/Binary
> Content-Length: 1413724
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
HTTP/1.1 100 Continue

* We are completely uploaded and fine
< HTTP/1.1 405 405
HTTP/1.1 405 405
< Date: Fri, 15 Mar 2019 06:35:49 GMT
Date: Fri, 15 Mar 2019 06:35:49 GMT
< Server: Apache/2.4.18 (Ubuntu)
Server: Apache/2.4.18 (Ubuntu)
< Set-Cookie:
JSESSIONID=4606702EDAC376EDE604CBB5500FC332;path=/;Secure;HttpOnly
Set-Cookie:
JSESSIONID=4606702EDAC376EDE604CBB5500FC332;path=/;Secure;HttpOnly
< Content-Language: en
Content-Language: en
< Content-Length: 1102
Content-Length: 1102
< Strict-Transport-Security: max-age=60
Strict-Transport-Security: max-age=60
< Content-Type: text/html;charset=utf-8
Content-Type: text/html;charset=utf-8

<
Apache Tomcat/8.5.11 - 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 {color:black;} .line
{height:1px;background-color:#525D76;border:none;}
HTTP Status 405 - HTTP method GET is not supported by this
URLtype Status
reportmessage HTTP method GET is not supported by this
URLdescription The specified HTTP method is not
allowed for the requested* Connection #0 to host
test.dspace-cris.4science.it left intact
 resource.Apache
Tomcat/8.5.11

*So my question is: is SwordV2 not supported in DSpaceCRIS?*

On Thu, 14 Mar 2019 at 09:56, Sean Carte  wrote:

> I'm trying to use swordv2 for depositing items to DSpace-CRIS 5.10 and am
> getting a 404 error.
>
> I am using the following curl command (pilfered from someone else's post):
>
> curl -v -i --data-binary "@Downloads/Singh_2009.pdf" -H
> "Content-Disposition:attachment; filename=Singh_2009.pdf" -H
> "Content-Type:application/pdf" -H "Packaging:
> http://purl.org/net/sword/package/Binary; -u sean.ca...@gmail.com:password
> -X POST http://dev-ir.dut.ac.za:8080/swordv2/collection/123456789/3119
>
> This is the response on the command line:
> Note: Unnecessary use of -X or --request, POST is already inferred.
> *   Trying 10.4.36.12...
> * Connected to dev-ir.dut.ac.za (10.4.36.12) port 8080 (#0)
> * Server auth using Basic with user 'sean.ca...@gmail.com'
> > POST /swordv2/collection/123456789/3119 HTTP/1.1
> > Host: dev-ir.dut.ac.za:8080
> > Authorization: Basic c2Vhbi5jYXJ0ZUBnbWFpbC5jb206MHJhbmRvbTA=
> > User-Agent: curl/7.47.0
> > Accept: */*
> > Content-Disposition:attachment; filename=Singh_2009.pdf
> > Content-Type:application/pdf
> > Packaging:http://purl.org/net/sword/package/Binary
> > Content-Length: 1413724
> > Expect: 100-continue
> >
> <

[dspace-tech] Swordv2 Deposit in DSpace-CRIS 5.10

[Sean Carte]

I'm trying to use swordv2 for depositing items to DSpace-CRIS 5.10 and am
getting a 404 error.

I am using the following curl command (pilfered from someone else's post):

curl -v -i --data-binary "@Downloads/Singh_2009.pdf" -H
"Content-Disposition:attachment; filename=Singh_2009.pdf" -H
"Content-Type:application/pdf" -H "Packaging:
http://purl.org/net/sword/package/Binary; -u sean.ca...@gmail.com:password
-X POST http://dev-ir.dut.ac.za:8080/swordv2/collection/123456789/3119

This is the response on the command line:
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying 10.4.36.12...
* Connected to dev-ir.dut.ac.za (10.4.36.12) port 8080 (#0)
* Server auth using Basic with user 'sean.ca...@gmail.com'
> POST /swordv2/collection/123456789/3119 HTTP/1.1
> Host: dev-ir.dut.ac.za:8080
> Authorization: Basic c2Vhbi5jYXJ0ZUBnbWFpbC5jb206MHJhbmRvbTA=
> User-Agent: curl/7.47.0
> Accept: */*
> Content-Disposition:attachment; filename=Singh_2009.pdf
> Content-Type:application/pdf
> Packaging:http://purl.org/net/sword/package/Binary
> Content-Length: 1413724
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
HTTP/1.1 100 Continue

* We are completely uploaded and fine
< HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
< Server: Apache-Coyote/1.1
Server: Apache-Coyote/1.1
< Content-Length: 0
Content-Length: 0
< Date: Thu, 14 Mar 2019 07:48:21 GMT
Date: Thu, 14 Mar 2019 07:48:21 GMT
< Connection: close
Connection: close

<
* Closing connection 0


And this is what I get in the dspace.log:

2019-03-14 09:53:02,522 INFO  org.swordapp.server.SwordAPIEndpoint @ Auth
type = Basic
2019-03-14 09:53:02,668 INFO  org.dspace.sword2.SwordAuthenticator @
anonymous:session_id=0:sword_authenticate:username=sean.ca...@gmail.com
,on_behalf_of=null
2019-03-14 09:53:02,669 INFO
org.dspace.authenticate.PasswordAuthentication @
anonymous:session_id=0:authenticate:attempting password auth of user=
sean.ca...@gmail.com
2019-03-14 09:53:02,965 INFO
org.dspace.authenticate.PasswordAuthentication @ sean.ca...@gmail.com:
session_id=0:authenticate:type=PasswordAuthentication
2019-03-14 09:53:02,965 INFO  org.dspace.sword2.DSpaceSwordAPI @
sean.ca...@gmail.com:session_id=0:sword_auth_request:username=
sean.ca...@gmail.com,on_behalf_of=NONE


I am able to submit items to that collection with that user using the
JSPUI. Is there something I'm doing wrong with swordv2?

-- 
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.