[dspace-tech] Playing in The DS8 Sandbox

[Chris Clawson]

I have been playing with submissions to the DS8 sandbox and have created a 
Top level Community as "User Chris" . I was pleased with the audio media 
player, thank you!

Is IIIF support enabled? I get a viewer window, but only see an embedded 
copy of the web page with a 404 error. This is an important feature we need 
to be comfortable with before upgrading our repository.

-- 
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/ae4b3545-4cad-41b0-b53d-ffbefeb76639n%40googlegroups.com.

[dspace-tech] Re: Restricted Collections Supporting IIIF in DSPace 8?

[Chris Clawson]

Thanks for the answer. I would do more if I had the technical ability. I am 
trying to offer DSpace to lay organizations, who are very defensive about 
their collections. Having the IIIF viewer is important in winning them 
over, but they insist in first having the collection private until 
accepted. I can't give them both the viewer as well as a restricted 
community, so they will likely just not accept DSpace.

On Tuesday, April 23, 2024 at 12:30:30 PM UTC-4 DSpace Technical Support 
wrote:

> Hi Chris & all,
>
> As of today, the DSpace 8 release will *not* include this feature as the 
> ticket is still open: https://github.com/DSpace/dspace-angular/issues/1435
>
> There was some early work done in a PR, but it had some security issues & 
> required more discussion: 
> https://github.com/DSpace/dspace-angular/pull/1436  At this time that 
> work seems "stalled" and is waiting on someone to pick it up again.
>
> Just as a reminder, new features to DSpace are all created by volunteers 
> or service providers <https://dspace.lyrasis.org/rsp/>.  We do not have a 
> centralized development team and we rely on the contributions from our 
> community of users.  I'd also love to see this feature in DSpace, but the 
> reality is that it requires someone to lead the effort and donate the work 
> back.  If anyone is interested, please feel free to volunteer via the 
> ticket above & let us know how you'd plan to resolve the issues in the 
> initial PR.
>
> Tim
>
> On Friday, April 12, 2024 at 12:49:35 PM UTC-5 Chris Clawson wrote:
>
>> Does this upcoming release permit IIIF/Mirador use in private collections 
>> and communities? This is important.
>>
>

-- 
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/e3b3562a-366b-4f71-bf36-2bd4b40ad336n%40googlegroups.com.

[dspace-tech] Tomcat optional in DSpace 8?

[Chris Clawson]

I am reading that DS 8 includes a runnable JAR (which includes Tomcat) and 
using this option ends the requirement to install Tomcat as a separate 
prerequisite. Is this now the preferred method?
My small server hosts both my Front and Backend. I have limited memory and 
the repository is slow to respond. Does this new embedded JAR run more 
efficiently or better conserve resources?
Please explain more or point me to a discussion..

-- 
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/a5d05b25-d39c-440c-b459-560c431f2704n%40googlegroups.com.

[dspace-tech] Restricted Collections Supporting IIIF in DSPace 8?

[Chris Clawson]

Does this upcoming release permit IIIF/Mirador use in private collections 
and communities? This is important.

-- 
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/b6ac9747-3511-47d5-83c2-38a047e3b2aan%40googlegroups.com.

Re: [dspace-tech] Unable to use IIIF in Private Community/Collection

[Chris Clawson]

Thank you! I am very sad to hear that by grateful for the answer, which 
prevents me from wasting more time on the problem. Please post a public 
procedure at such time that one might support the DSpace core release.
Chris

On Thursday, September 21, 2023 at 2:48:24 AM UTC-4 Bollini, Andrea wrote:

> Using IIIF over restricted content is not currently supported out-of-box 
> by DSpace. It requires some customization and careful configuration of the 
> infrastructure.
> We, at 4Science, are currently able to manage that with our commercial 
> extension.
> With the community we are working for a long term solution in the official 
> DSpace see https://github.com/DSpace/dspace-angular/issues/1435
>
> Andrea
>
>
> -- 
> Andrea Bollini
> Chief Technology and Innovation Officer
>
> 4Science, www.4science.com, ISO 9001:2015, CSA Trusted Cloud Provider
> Certified Platinum Provider of DSpace, DSpace-CRIS, DSpace-GLAM
>
> 4Science USA - 435 Nichols Road Suite 200, Kansas City, MO 64112
> 4Science Europe - Viale Achille Papa 30, World Join Center Tower, 20149 
> Milano, Italy
> mobile: +39 333 934 1808 <+393339341808>
> linkedin: andreabollini
> orcid: -0002-9029-1854
> --
> *From:* dspac...@googlegroups.com  on behalf 
> of DSpace Technical Support 
> *Sent:* Monday, September 18, 2023 8:36 PM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Unable to use IIIF in Private 
> Community/Collection 
>  
> I am trying to provide Mirador and IIIF image viewing in a Community and 
> Collection restricted from public view.
> I have a special user group defined and have set default read, write and 
> submit privileges to that group.
> EPerson members of that group will see the community once they have logged 
> in. I have one Collection defined and the one Item within that Collection 
> has dspace.iiif.enabled set to 'true'.
> When I view the item, the Mirador viewer draws but there is nothing inside 
> the viewer. No error is reported and no metadata is displayed.
> All of my public Communities and Items (with IIIF enabled) display 
> normally. It is only this restricted community which won't display IIIF 
> content.
> Might somebody help me solve this problem, please? I am happy to provide 
> more detail.
>
> -- 
> 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/4a3a19ed-0737-41f5-8e3a-ddaf029d7084n%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/d27871a5-e1d7-4329-afca-60268e919e0dn%40googlegroups.com.

[dspace-tech] Re: IIIF PDF manifest not complete

[Chris Clawson]

Has anybody done this successfully? Might you please point us to a clear 
procedure to set it up? I am using DSpace 7.6

On Tuesday, August 15, 2023 at 9:05:21 AM UTC-4 Muhep Atasoy wrote:

> Same. Dspace 7.6
>
> 10 Ocak 2023 Salı tarihinde saat 01:21:08 UTC+3 itibarıyla Natalia 
> Jabinschi şunları yazdı:
>
>> For the installed version 7.4, we activated the IIIF option, everything 
>> seems correct, Mirador displays image files well, but it is not able to 
>> display PDF files. The Cantaloupe server does not give errors and is able 
>> to create json and jpg files. When we analyze the Manifest we see that the 
>> "canvases" parameter is empty for PDF. It is not clear if we need to 
>> configure something special for PDF files accessed through IIIF.
>>
>> .
>> "rendering":{
>>   "@id":"
>> https://papyrus-test.bib.umontreal.ca/server/api/core/bitstreams/4933a23e-3910-44c8-a0d9-c8768ef86fb7/content
>> ",
>>   "label":"mirador-test-pdf.pdf",
>>   "format":"application/pdf"
>>},
>>"sequences":[
>>   {
>>  "@id":"
>> https://papyrus-test.bib.umontreal.ca/server/iiif/4949a3de-3cfe-4c54-ac21-26c02a8f9432/sequence/s0
>> ",
>>  "@type":"sc:Sequence",
>>  "canvases":[
>> 
>>  ]
>>   }
>> 
>>
>> Thank you for the help
>>
>

-- 
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/848f5161-1db3-46fb-938b-f6f644ab3a81n%40googlegroups.com.

[dspace-tech] An issue with AIP import?

[Chris Clawson]

Please check my attempt! I have exported several items from my production 
server. I attempted to import them to my test system as new items to a test 
collection. These items exist elsewhere in my test system, but isn't that 
okay when using -s submit mode?
My test collection handle is MHS-01376/6883. The entire command line import 
was:
/opt/dspace/bin/dspace packager -s -t AIP -e ch...@x.org -p 
MHS-01376/6883 /home/chrisc/export2/6563.zip . I expected a new item to be 
added to MHS-01376/6883

The terminal responded with:
/opt/dspace/bin/dspace packager -s -t AIP -e ch...@x.org -p 
MHS-01376/6883 /home/chrisc/export2/6563.zip
Destination parents:
Owner: MHS-01376/6883
Ingesting package located at /home/chrisc/export2/6563.zip
CREATED new DSpace ITEM [ hdl=MHS-01376/6563, 
dbID=4ec3be54-d47d-4a46-bb9e-5c665c7aaba7 ]

## NO! it used the original item handle, rather than assigning a new 
one. The importer copied the archive contents to the existing 
MHS-01376/6563 (in the other collection), duplicating all the metadata and 
bitstreams, besides clobbering the 33 image iiif gallery.
Please comment and show me what I am doing wrong.
C. (using DSpace 7.6)

-- 
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/c58ec1d6-866c-4d30-9bf0-b1aecdb795c9n%40googlegroups.com.

[dspace-tech] An issue with AIP import?

[Chris Clawson]

Please check my attempt! I have exported sever items from my production 
server. I attempted to import them to my test system as new items to a test 
collection. These items exist elsewhere in my test system, but isn't that 
okay when using -s submit mode?
My test collection handle is MHS-01376/6883. The entire command line import 
was:
/opt/dspace/bin/dspace packager -s -t AIP -e ch...@x.org -p 
MHS-01376/6883 /home/chrisc/export2/6563.zip . I expected a new item to be 
added to MHS-01376/6883

The terminal responded with:
/opt/dspace/bin/dspace packager -s -t AIP -e ch...@x.org -p 
MHS-01376/6883 /home/chrisc/export2/6563.zip
Destination parents:
Owner: MHS-01376/6883
Ingesting package located at /home/chrisc/export2/6563.zip
CREATED new DSpace ITEM [ hdl=MHS-01376/6563, 
dbID=4ec3be54-d47d-4a46-bb9e-5c665c7aaba7 ]

## NO! it used the original item handle, rather than assigning a new 
one. The importer copied the archive contents to the existing 
MHS-01376/6563, duplicating all the metadata and bitstreams, besides 
clobbering the 33 image iiif gallery.
Please comment and show me what I am doing wrong.
C. DSpace 7.6

-- 
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/1aea43d5-f18f-4421-8787-fc54e7752e64n%40googlegroups.com.

[dspace-tech] Re: An issue with AIP import?

[Chris Clawson]

Sorry - This is using DSpace 7.6

On Monday, July 31, 2023 at 7:27:34 PM UTC-4 Chris Clawson wrote:

> Please check my attempt! I have exported sever items from my production 
> server. I attempted to import them to my test system as new items to a *test 
> collection*. These items exist elsewhere in my test system, but isn't 
> that okay when using -s submit mode?
> My test collection handle is MHS-01376/6883. The entire command line 
> import was:
> /opt/dspace/bin/dspace packager -s -t AIP -e ch...@x.org -p 
> MHS-01376/6883 /home/chrisc/export2/6563.zip . I expected a new item to be 
> added to MHS-01376/6883 
>
> The terminal responded with:
> /opt/dspace/bin/dspace packager -s -t AIP -e ch...@x.org -p 
> MHS-01376/6883 /home/chrisc/export2/6563.zip
> Destination parents:
> Owner: MHS-01376/6883
> Ingesting package located at /home/chrisc/export2/6563.zip
> CREATED new DSpace ITEM [ hdl=MHS-01376/6563, 
> dbID=4ec3be54-d47d-4a46-bb9e-5c665c7aaba7 ]
>
> ## NO! it used the original item handle, rather than assigning a new 
> one. The importer copied the archive contents to the existing 
> MHS-01376/6563, duplicating all the metadata and bitstreams, besides 
> clobbering the 33 image iiif gallery.
> Please comment and show me what I am doing wrong.
> C.
>

-- 
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/25eb6aa8-9e78-4c5a-91b2-d1f174088ef4n%40googlegroups.com.

[dspace-tech] An issue with AIP import?

[Chris Clawson]

Please check my attempt! I have exported sever items from my production 
server. I attempted to import them to my test system as new items to a *test 
collection*. These items exist elsewhere in my test system, but isn't that 
okay when using -s submit mode?
My test collection handle is MHS-01376/6883. The entire command line import 
was:
/opt/dspace/bin/dspace packager -s -t AIP -e ch...@x.org -p 
MHS-01376/6883 /home/chrisc/export2/6563.zip . I expected a new item to be 
added to MHS-01376/6883 

The terminal responded with:
/opt/dspace/bin/dspace packager -s -t AIP -e ch...@x.org -p 
MHS-01376/6883 /home/chrisc/export2/6563.zip
Destination parents:
Owner: MHS-01376/6883
Ingesting package located at /home/chrisc/export2/6563.zip
CREATED new DSpace ITEM [ hdl=MHS-01376/6563, 
dbID=4ec3be54-d47d-4a46-bb9e-5c665c7aaba7 ]

## NO! it used the original item handle, rather than assigning a new 
one. The importer copied the archive contents to the existing 
MHS-01376/6563, duplicating all the metadata and bitstreams, besides 
clobbering the 33 image iiif gallery.
Please comment and show me what I am doing wrong.
C.

-- 
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/308c995f-eedd-48e5-96ce-cf2d600853edn%40googlegroups.com.

[dspace-tech] Re: AIP import - bug or my error?

[Chris Clawson]

I solved my problem (with Tim's suggestion) I didn't see any examples given 
for the -r restore option, which include specifying a parent directory. The 
following example does work. I just included the -p option to specify the 
new parent collection.  This now takes an old, single item AIP and 
'restores" it to a more recently created collection (MHS-01376/6864):
[dspace]/bin/dspace packager -r -a -k -t AIP -e ch...@mydomain.org -p 
MHS-01376/6864 i...@mhs-01376-5381.zip
Thanks for the direction

On Friday, July 28, 2023 at 5:09:37 PM UTC-4 Chris Clawson wrote:

> Thanks Tim,
> But I don't see any option with the  -R restore command to direct the 
> import to a new collection. The original collection no longer exists, so 
> how will the restore -r command work if the target collection no longer 
> exists?  My Wordpress site still refers to this old item and it's URI. I 
> prefer to direct it to a specific (and new) collection, but don't care too 
> much where it goes because I can always move it around later. I do need to 
> keep the item URI to respect the references elsewhere.
>
> On Wednesday, July 26, 2023 at 2:45:48 PM UTC-4 DSpace Technical Support 
> wrote:
>
>> Hi Chris,
>>
>> I think you might be missing the "-r" flag to tell the packager command 
>> that you want to use *restore* mode.  This will also default to setting 
>> "ignoreHandle=false", so that option shouldn't be needed.  See the 
>> instructions at 
>> https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore#AIPBackupandRestore-DefaultRestoreMode
>>
>> By default, if you don't specify "-r", then it defaults to "submit" mode 
>> which tries to assign a new URI.  For more on the differences between 
>> Submit & Restore, see this section of the docs:  
>> https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore#AIPBackupandRestore-IngestionModes
>>
>> That said, it does seem like the "ignoreHandle=false" option should have 
>> also worked with your command.  Not sure why it would not have worked, but 
>> you also may want to check the logs to see if there were errors reported.
>>
>> Tim
>>
>> On Tuesday, July 25, 2023 at 6:31:09 PM UTC-5 Chris Clawson wrote:
>>
>>> I just attempted to import an item that had been exported and deleted. I 
>>> wish to import it back to a new collection but want to preserve the 
>>> original and full handle. The importer imports the item only as new, 
>>> seemingly ignoring the -o option. 
>>> The example:
>>> /opt/dspace/bin/dspace packager -o ignoreHandle=false -t AIP -e 
>>> ch...@mydomain.org -p MHS-01376/6742 
>>> /home/chris/it...@mhs-01376-5381.zip
>>> A new item is created as MHS-01376-6855 and then added to my expected 
>>> collection. I want to keep the MHS-01376-5381 URI.
>>>
>>> I refer to this old URI in my wordpress site and don't want to run 
>>> around my blog posts and rename many occurrences of these newly restored 
>>> items. I have tried both "false" and "true" -o options, but neither 
>>> restores the original handle,  using this command.
>>> Might somebody correct me, please? (This handle has not need reassigned 
>>> in my existing db).
>>> DSpace 7.6
>>>
>>

-- 
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/fd8ab807-4031-4626-af32-f9729025e31dn%40googlegroups.com.

[dspace-tech] Re: AIP import - bug or my error?

[Chris Clawson]

Thanks Tim,
But I don't see any option with the  -R restore command to direct the 
import to a new collection. The original collection no longer exists, so 
how will the restore -r command work if the target collection no longer 
exists?  My Wordpress site still refers to this old item and it's URI. I 
prefer to direct it to a specific (and new) collection, but don't care too 
much where it goes because I can always move it around later. I do need to 
keep the item URI to respect the references elsewhere.

On Wednesday, July 26, 2023 at 2:45:48 PM UTC-4 DSpace Technical Support 
wrote:

> Hi Chris,
>
> I think you might be missing the "-r" flag to tell the packager command 
> that you want to use *restore* mode.  This will also default to setting 
> "ignoreHandle=false", so that option shouldn't be needed.  See the 
> instructions at 
> https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore#AIPBackupandRestore-DefaultRestoreMode
>
> By default, if you don't specify "-r", then it defaults to "submit" mode 
> which tries to assign a new URI.  For more on the differences between 
> Submit & Restore, see this section of the docs:  
> https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore#AIPBackupandRestore-IngestionModes
>
> That said, it does seem like the "ignoreHandle=false" option should have 
> also worked with your command.  Not sure why it would not have worked, but 
> you also may want to check the logs to see if there were errors reported.
>
> Tim
>
> On Tuesday, July 25, 2023 at 6:31:09 PM UTC-5 Chris Clawson wrote:
>
>> I just attempted to import an item that had been exported and deleted. I 
>> wish to import it back to a new collection but want to preserve the 
>> original and full handle. The importer imports the item only as new, 
>> seemingly ignoring the -o option. 
>> The example:
>> /opt/dspace/bin/dspace packager -o ignoreHandle=false -t AIP -e 
>> ch...@mydomain.org -p MHS-01376/6742 /home/chris/it...@mhs-01376-5381.zip
>> A new item is created as MHS-01376-6855 and then added to my expected 
>> collection. I want to keep the MHS-01376-5381 URI.
>>
>> I refer to this old URI in my wordpress site and don't want to run around 
>> my blog posts and rename many occurrences of these newly restored items. I 
>> have tried both "false" and "true" -o options, but neither restores the 
>> original handle,  using this command.
>> Might somebody correct me, please? (This handle has not need reassigned 
>> in my existing db).
>> DSpace 7.6
>>
>

-- 
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/dc41b12b-7e51-4b35-9dfb-2178fe41cf3dn%40googlegroups.com.

[dspace-tech] AIP import - bug or my error?

[Chris Clawson]

I just attempted to import an item that had been exported and deleted. I 
wish to import it back to a new collection but want to preserve the 
original and full handle. The importer imports the item only as new, 
seemingly ignoring the -o option. 
The example:
/opt/dspace/bin/dspace packager -o ignoreHandle=false -t AIP -e 
ch...@mydomain.org -p MHS-01376/6742 /home/chris/i...@mhs-01376-5381.zip
A new item is created as MHS-01376-6855 and then added to my expected 
collection. I want to keep the MHS-01376-5381 URI.

I refer to this old URI in my wordpress site and don't want to run around 
my blog posts and rename many occurrences of these newly restored items. I 
have tried both "false" and "true" -o options, but neither restores the 
original handle,  using this command.
Might somebody correct me, please? (This handle has not need reassigned in 
my existing db).
DSpace 7.6

-- 
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/3634c0a6-9393-42ee-a395-043b063ad0f2n%40googlegroups.com.

[dspace-tech] Hidden Communities or Collections in 7.6

[Chris Clawson]

I am getting a bit worried... 
How may I hide all the content inside a community or sub-community and make 
it all public when I am ready? I can hide communities from being listed to 
an anonymous visitor, but they still may do a search and find any of the 
content I thought was hidden. The "Recently added list at the page bottom 
also proudly displays content I want hidden. Let's presume all this content 
exist only under the Top-Level Community I wish to keep private.

I understand that individual items have a 'status' button to allow them to 
become private. How about an entire collection or community?
What if I had a client who wished to build a community only for private use?

-- 
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/7af8a549-e7a3-45e7-9a0d-f168d40b343dn%40googlegroups.com.

[dspace-tech] Re: limited bitstream permission and Mirador

[Chris Clawson]

I have been asked to do this as well. Does anybody know a method?

On Monday, April 3, 2023 at 7:23:00 AM UTC-4 Evelin Bányai wrote:

> Hello,
>
> There are certain items we would like to have with withdrawn_read 
> bitstream permission so the users should ask for permission to download the 
> full picture. However, if we setup up the item with such permission the 
> built-in Mirador viewer won't show anything.
>
> Is there a way to set up such configuration where the file download is 
> limited but the viewer able to show the image? I have my doubts, but it's 
> worth a try to ask.
>
> We have version 7.2.1.
>
> Thanks!
> Evelin
>

-- 
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/9daab2b7-5417-4178-a6ca-1553067e4eb6n%40googlegroups.com.

[dspace-tech] Re: Fields available in metadata export

[Chris Clawson]

I checked this file inside my DS 7.2 installation. Here is the entry I 
would expect to control the terms:

# Metadata elements to exclude when exporting via the user interfaces, or 
when using the
# command line version and not using the -a (all) option.
# bulkedit.ignore-on-export = dc.date.accessioned, dc.date.available, \
#dc.date.updated, dc.description.provenance

Please notice this feature is already commented out, yet the terms are not 
being exported in the CSV. Is this a 7.2 bug or is the export of these 
terms also controlled somewhere else?

On Thursday, July 7, 2022 at 11:34:45 AM UTC-4 al...@vt.edu wrote:

> The dc.description.provenance is a hidden field by default so it is not 
> exported by default in the XMLU interface for DSpace 6.3. 
> https://wiki.lyrasis.org/display/DSDOC6x/Batch+Metadata+Editing#BatchMetadataEditing-WebInterfaceExport
>  
> has instructions for including additional fields.It looks like the 
> configuration file for this is [dspace]/config/modules/bulkedit.cfg .
>
> Anne
>
> On Wednesday, July 6, 2022 at 2:21:00 PM UTC-4 Chris Clawson wrote:
>
>> Do I remember the dc.provenance being exported with metadata in earlier 
>> versions? When I export collection metadata in DS 7.2, I no longer see any 
>> fields included which report the original bitstream filenames, which is 
>> important to us.
>> Might someone please describe the location and config files that control 
>> which fields are exported to CSV? How may I configure this?
>>
>

-- 
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/41f2e8da-cd8e-4209-a1d9-97b3733bdc72n%40googlegroups.com.

[dspace-tech] Fields available in metadata export

[Chris Clawson]

Do I remember the dc.provenance being exported with metadata in earlier 
versions? When I export collection metadata in DS 7.2, I no longer see any 
fields included which report the original bitstream filenames, which is 
important to us.
Might someone please describe the location and config files that control 
which fields are exported to CSV? How may I configure this?

-- 
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/25d5518f-e693-4748-a4ff-62f88e4408een%40googlegroups.com.

[dspace-tech] Re: Running out of hardware resources?

[Chris Clawson]

Well, no hard and repeatable errors. Dragging a group of images (at one 
time) into an item may unpredictably fail individual images, while 
correctly uploading others. If an item contains 30 images, the iiif server 
takes time to generate the thumbnails in the navigator bar. To repeat, I 
might get into big trouble if our server ever experienced any real demand. 
Since this posting, we have added an additional 1GB of ram. The 
installation quickly found it and we are back to about 140Mb of free 
memory, although I notice the cache memory settles around 900Mb. Over all, 
I suppose we are doing well for a $20/mo. virtual machine.

On Tuesday, May 31, 2022 at 3:36:58 PM UTC-4 Tim Donohue wrote:

> Hi Chris,
>
> You haven't let us know what sort of errors you are seeing... but, it does 
> (at a glance) sound like you are running a *lot* under very little 
> resources.  It sounds like you are running DSpace + Wordpress  (and all 
> their pre-requisites) with just 4GB of memory total?  That's impressive, as 
> I'd expect either DSpace alone would want at least 4GB of memory (and 
> Wordpress may require something similar).
>
> Overall, if you want to run everything DSpace requires on one server, I 
> think you'd need 4GB at a minimum *just for DSpace*.  Inspired by your 
> question, I went ahead and wrote up some "bare minimum requirements" based 
> on what works for me on a memory-controlled Docker setup of DSpace 7.
>
>
> https://wiki.lyrasis.org/display/DSDOC7x/Performance+Tuning+DSpace#PerformanceTuningDSpace-BareMinimumRequirements
>
> I believe these requirements to be accurate, but it's possible we'll need 
> to tweak them based on what others report in production scenarios.  In any 
> case, I do think you will need to think about either adding RAM, or 
> alternatively finding a separate server for either the frontend or backend 
> (as you do not need to run both on the same server).  You also may need to 
> look closely at Wordpress & MysSQL memory requirements, as they could also 
> have an impact on your memory usage & therefore DSpace's performance.
>
> Tim
>
> On Saturday, May 28, 2022 at 9:47:01 AM UTC-5 Chris Clawson wrote:
>
>>
>>
>> What are the reliable minimum server requirements for a DSpace 7 
>> installation? 
>>
>> Our installation is funded out-of-pocket and we just can't afford the 
>> kind of professional hosting expected for major institutions. 
>>
>> Am I running out of system resources? Here is my overview:
>>
>> Non-managed KVM virtual server
>>
>> Ubuntu 20.04
>>
>> 4 CPU cores
>>
>> 4GB RAM
>>
>> 1GB swap
>>
>> The system load is very light, but RAM usage is now typically 97% 
>> capacity and swap varies around 80%. We have items with 30 or more images. 
>> The Mirador viewer does work reliably, but the thumbnail generation is 
>> taking more time than we'd like to see. 
>>
>> Tomcat 9
>>
>> Apache 2
>>
>> PostgreSQL
>>
>> MySQL
>>
>> Cantaloupe image server
>>
>>
>> DSpace 7.2
>>
>> Wordpress
>>
>> Would another GB of RAM speed performance up and prevent bitstream upload 
>> errors? It will cost more to find out.
>>
>

-- 
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/ba4e9798-23cf-466a-b3b1-b63b9f8d0facn%40googlegroups.com.

[dspace-tech] Running out of hardware resources?

[Chris Clawson]

What are the reliable minimum server requirements for a DSpace 7 
installation? 

Our installation is funded out-of-pocket and we just can't afford the kind 
of professional hosting expected for major institutions. 

Am I running out of system resources? Here is my overview:

Non-managed KVM virtual server

Ubuntu 20.04

4 CPU cores

4GB RAM

1GB swap

The system load is very light, but RAM usage is now typically 97% capacity 
and swap varies around 80%. We have items with 30 or more images. The 
Mirador viewer does work reliably, but the thumbnail generation is taking 
more time than we'd like to see. 

Tomcat 9

Apache 2

PostgreSQL

MySQL

Cantaloupe image server


DSpace 7.2

Wordpress

Would another GB of RAM speed performance up and prevent bitstream upload 
errors? It will cost more to find out.

-- 
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/3eab0d42-14d1-46bc-ac4c-850e4d397a6bn%40googlegroups.com.

[dspace-tech] Re: Relationships problem and question

[Chris Clawson]

I was unable to post the bug to GitHub, because of my account status. Below 
is my report. Might you or somebody please Submit it?
**   

*Invalid data in dspace.entity.type makes item uneditable*

DSpace Angular 7.2

Ubuntu 20.04 web server

*Accidental or improper entries in an item's dspace.entity.type metadata 
causes the item to hang DSpace when attempting to view or edit. The item 
may only then be fixed by importing a data corrected CSV spreadsheet.*

*Repeatable prodedure:*

Select a normal and good item and edit the contents of dspace.entity.type 
with the following:

Couture Bros., Turners Falls, Montague, Franklin County

(This was the data erroneously added in the original problem)

Once saved, the item will display in Collection summaries (showing the bad 
data as an entity) but will hang DSpace and prevent viewing, editing or 
deletion.


*Discussion:*

This was caused in error by an associate with admin privileges who mistook 
the 'Relationships' tab for a place to enter keywords. I was also able to 
find this tab active (with a drop down menu), but have since found it only 
saying “Add 'dspace.entity.type' metadata to enable relationships for this 
item “. The main Metadata Edit tab shows 'dspace.entity.type' as being 
defined, but with no data in the cell. I still do not know how to activate 
this 'Relationships' tab and repeat the exact scenario I believe led to the 
problem.

(corrupted exports?)

I also originally had Collection level metadata exports either failing or 
providing the wrong collections. I was able to fix the original problem by 
successfully exporting at the Community level, deleting the contents of the 
bad cell and then importing back that row to DSpace.

I am sorry I can't repeat the other points raised in this discussion, but 
hopefully focusing on the repeatable portion will prevent the other stuff 
in the future.




On Thursday, May 12, 2022 at 11:25:38 AM UTC-4 Tim Donohue wrote:

> Hi Chris,
>
> While the "dspace.entity.type" metadata field does exist in the database 
> by default, it is not used by default in the submission forms, etc.  So, 
> you shouldn't need to modify any configurations to disable that field from 
> being used in the creation/deposit process.
>
> However, it seems you are correct that it *is* possible for an 
> Administrator to add a "dspace.entity.type" metadata field to an existing 
> Item if they edit the Item, search for that field and add it manually to 
> the Item.  This is unlikely to occur, but it is a possible mistake someone 
> could make (and it sounds like that happened for you).   
>
> The odd thing though is that adding an invalid "dspace.entity.type" should 
> NOT block your ability to delete or edit the Item.  That was a bug in 7.1, 
> but we fixed it in 7.2 in this PR: 
> https://github.com/DSpace/dspace-angular/pull/1503  So, that's confusing 
> to me why you still experienced this bug.
>
> If you have the time to document how this occurred, or (if you have a test 
> site which you can play with) you are willing to try and reproduce the 
> issue, it'd be very useful to use if you could create a bug ticket in 
> https://github.com/DSpace/dspace-angular/issues   It sounds like you've 
> hit some behavior that is entirely unexpected, and either we should 
> consider blocking people from manually adding the "dspace.entity.type" 
> field, or find a way to ensure that doing so doesn't cause unexpected 
> errors.   But, in order to track that down, we'd need more information on 
> how to potentially reproduce this bug in an issue ticket.
>
> Thanks,
>
> Tim
>
> On Thursday, May 12, 2022 at 10:01:07 AM UTC-5 Chris Clawson wrote:
>
>>  I understand that 'Relationships' and configurable entities are now part 
>> of DS Angular 7.2. It seems to be controlled by a new (?) metadata term, 
>> 'dspace.entity.type' , which enabled the ability to edit values under the 
>> Edit> Relationships tab. This term now seems enabled by default when a new 
>> item is created.
>>
>> We are not planning to use this feature in the near future and one of our 
>> editors mistakenly just entered invalid data into this term while editing 
>> an item. This changed the item into an undefined entity. The caused the  
>> item to be uneditable and we could not delete it. It also may have 
>> corrupted metadata exports at the collection level.
>>
>> Fortunately, I was able to correctly export Community metadata as a CSV 
>> spreadsheet. A column for the term 'dspace.entity.type' was defined and I 
>> was able to find and delete the cell with the bad data. Importing the 
>> correcting, single row csv fixed my problem for this item and I was then 
>> able to edit the item and normally export collection 

[dspace-tech] Relationships problem and question

[Chris Clawson]

 I understand that 'Relationships' and configurable entities are now part 
of DS Angular 7.2. It seems to be controlled by a new (?) metadata term, 
'dspace.entity.type' , which enabled the ability to edit values under the 
Edit> Relationships tab. This term now seems enabled by default when a new 
item is created.

We are not planning to use this feature in the near future and one of our 
editors mistakenly just entered invalid data into this term while editing 
an item. This changed the item into an undefined entity. The caused the  
item to be uneditable and we could not delete it. It also may have 
corrupted metadata exports at the collection level.

Fortunately, I was able to correctly export Community metadata as a CSV 
spreadsheet. A column for the term 'dspace.entity.type' was defined and I 
was able to find and delete the cell with the bad data. Importing the 
correcting, single row csv fixed my problem for this item and I was then 
able to edit the item and normally export collection metadata.

Question: Can/should I disable the default addition of this term when 
creating a new item? Can someone provide a config file and method to do 
this? We could always enable it later, right?

-- 
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/e448e2c8-f24a-49b0-b259-b23b25b79f40n%40googlegroups.com.

[dspace-tech] IIIF and Jpeg2000 now working! - Here's How

[Chris Clawson]

The following procedure succeeded in enabling Jpeg2000 (JP2) format images 
to be served out of DSpace 7.2, under the new IIIF support with the 
Cantaloupe 5 image server installed and items enabled with the specifically 
added metadata value 'dspace.​iiif.​enabled ' and a value of 'true' set. 
This is a web server running under Ubuntu 20.04.

It took me a while to understand that with iiif, it is this new image 
server which delivers images to the client. DSpace is showing the user an 
iiif enabled item and the Mirador viewer has requested a default display of 
the image (from Cantaloupe). The user then may choose a full screen view or 
any other sort of zoom level. The viewer makes updated requests to the 
Cantaloupe image server and it responds with the new data.

This has all worked fine for my DS7.2 install, except our limited storage 
has prevented uploading large size image files. The JPEG2000 format is very 
efficient in multiple resolution images and is capable of amazing levels of 
good looking compression ratios, so this seemed to be the best option for 
us to support IIIF. It didn't work with our default installation. Here is 
how we fixed it:

The mime type 'image/jp2' is not defined in the DSpace Bitstream Format 
registry. Without defining this, you will not be able to serve the images.

  
   1. 
   
   (Logged in as administrator) go toRegistries > Format. This opens 
   the Bitstream Format Registry.   
   2. 
   
   (Green button) “Add a newbitstream format”.   
   3. 
   
   (add the following) Name =image/jp2, MIME Type = image/jp2, 
   Description = Jpeg2000, Fileextensions = jp2 (save)
   
This will allow the image to be properly recognized when added to the item.

Your server now probably needs libraries to tell the Cantaloupe image 
server how to deal with the jpeg2000 images. My site has installed the 
OpenJpeg libraries, with the following command:   

apt install libopenjp2-7   libopenjp2-tools -y   

Now edit the cantaloupe.properties configuration file. Mine is located at 
/opt/cantaloupe_config .   

vi  /opt/cantaloupe_config/cantaloupe.properties  

Edit this file to define the following   

a) processor.selection_strategy = ManualSelectionStrategy

b) processor.ManualSelectionStrategy.jp2 = OpenJpegProcessor
c) OpenJpegProcessor.path_to_binaries= /usr/bin/opj_decompress


   
7. (Save the file) 
   
  
   
   8. (restart Cantaloupe) systemctl restart cantaloupe.service   
   
   You may check Cantaloupe's status bythe command = 
   
   systemctl status cantaloupe.service 
   
   and see areturning message, like:   
   
   ( Format.JPEG2000:  
   com.sun.media.imageioimpl.plugins.jpeg2000.J2KImageWriter )
   
You may now create new items and add bitstream images of the jp2 format. 
CAUTION, it is not all that common to have transcoding software that can 
produce compatible jp2. Some of my utilities claim they can but they do not 
work with DSpace. I have been having good luck using Irfanview and even 
ImageMagick. Much more experimentation is needed here to create the 
perfect, zoomable image. I hope this is a useful start for those 
interested.   

Thank you so much to Mohammad S. AlMutairi and Tim Donohue for providing 
critical information in getting this to work!


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

[dspace-tech] Re: JP2 questions

[Chris Clawson]

Isn't JP2 defined in Dspace's metadata registry? If I were to define that, 
could I them add Jpeg2000 images as bitstreams and have them served by 
Cantaloupe?

On Saturday, April 23, 2022 at 9:47:46 PM UTC-4 Chris Clawson wrote:

> I am using DSpace 7.2, with the Mirador viewer and Cantaloupe. I am unable 
> to get my first attempts to use JP2 (jpeg2000) to view anywhere. When 
> uploading as a bitstream, DSpace complains "unknown format". I have 
> produced these jp2 images from png using imagemagick. The resulting images 
> view well using Irfanview. I also downloaded a sample JP2 file and got the 
> same results.
> Isn't JP2 enabled by default? How/where do I check? Suggestions for 
> troubleshooting?
> C.
>

-- 
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/df467041-7674-430a-84a7-cede50861ba9n%40googlegroups.com.

[dspace-tech] JP2 questions

[Chris Clawson]

I am using DSpace 7.2, with the Mirador viewer and Cantaloupe. I am unable 
to get my first attempts to use JP2 (jpeg2000) to view anywhere. When 
uploading as a bitstream, DSpace complains "unknown format". I have 
produced these jp2 images from png using imagemagick. The resulting images 
view well using Irfanview. I also downloaded a sample JP2 file and got the 
same results.
Isn't JP2 enabled by default? How/where do I check? Suggestions for 
troubleshooting?
C.

-- 
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/00a0d409-a07f-4fa0-967c-ed7819ed53den%40googlegroups.com.

[dspace-tech] Re: Moving Bitstreams to other Items?

[Chris Clawson]

Thanks for the answer. For now, it may be just safer to export AIPs and 
Community/Collection metadata, and then develop methods to build working 
directories offline for later import. Such exports will provide all the 
images and records of anything needed for future items and also make it 
possible to create a new CSV of obsolete items to delete later. 

On Friday, April 22, 2022 at 3:57:17 PM UTC-4 Tim Donohue wrote:

> Hi Chris,
>
> At this time, I'm not aware of a way to move Bitstreams between Items... 
> other than at the database level.   
>
> Hypothetically, you should be able to move a Bitstream by changing the 
> "bundle2bitstream" table in the database, as that table decides which 
> Bundle each Bitstream belongs to.  So, it may be possible to move them by 
> moving them from one Item's "ORIGINAL" Bundle to another Item's "ORIGINAL" 
> Bundle. (The "ORIGINAL" Bundle is just the default Bundle that DSpace uses 
> to store bitstreams).   If you move Bitstreams in this way, you will *have* 
> to do a full reindex of the site (otherwise your search results will likely 
> show the old location).  I'd also recommend trying this out in a 
> test/staging environment first, as I've never done this before... so, you 
> want to make sure it works with no side effects.
>
> Unfortunately, I do not believe this is possible from the REST API or UI 
> at this time.  (If I'm wrong about that, I hope someone corrects me!)  The 
> only way to achieve something similar from the UI would be to download the 
> file from one Item and then upload it to a different Item, but that'd be a 
> very manual process.
>
> Tim
>
> On Thursday, April 21, 2022 at 7:45:53 AM UTC-5 Chris Clawson wrote:
>
>> We have many items in our database which include single images.  Many of 
>> these should  be combined into groups and described by a single entry.
>>
>> The new image viewer and image metadata (description) makes it much 
>> better for users to view a single item, containing larger groups of images. 
>> The viewer now permits gallery views or 'slide show' presentation and the 
>> user doesn't need to jump around database items to view a related group of 
>> images.
>>
>> How can I move previously assigned  bitstreams to these newly created 
>> items?
>>
>>

-- 
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/4501404f-9c7f-4279-9aaa-36376b61a4a4n%40googlegroups.com.

[dspace-tech] Moving Bitstreams to other Items?

[Chris Clawson]

We have many items in our database which include single images.  Many of 
these should  be combined into groups and described by a single entry.

The new image viewer and image metadata (description) makes it much better 
for users to view a single item, containing larger groups of images. The 
viewer now permits gallery views or 'slide show' presentation and the user 
doesn't need to jump around database items to view a related group of 
images.

How can I move previously assigned  bitstreams to these newly created items?

-- 
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/264c406a-640f-49d1-9b22-8f50125e8217n%40googlegroups.com.

[dspace-tech] Re: Broken Mirador/ iiif viewer with 7.2.1 patch?

[Chris Clawson]

Great. Yes, my problem was in iiif.cfg pointing to the old image server 
address (an obsolete version of the file).
Thanks for the help and I apologize for not catching this.

On Wednesday, April 6, 2022 at 11:11:10 AM UTC-4 Tim Donohue wrote:

> Chris,
>
> Since you are getting a CORS (Cross-Origin Request) Error, I suspect this 
> has something to do with your configuration.  It looks like it says it's 
> not allowing you to access http://localhost:8182/... which means that 
> origin is possibly missing from your "rest.cors.allowed-origins" setting in 
> your local.cfg?  
> https://github.com/DSpace/DSpace/blob/main/dspace/config/local.cfg.EXAMPLE#L227
>
> That's my best guess. It doesn't sound like it's related to the 7.2.1 
> patch... instead, it sounds like perhaps your update accidentally *removed* 
> a setting you had in place previously.  I'd recommend double checking your 
> configs...and moving *all* your custom configurations (in any *.cfg files) 
> into your local.cfg (as that file will never be overwritten during an 
> upgrade/update).
>
> Tim
> On Wednesday, April 6, 2022 at 9:30:24 AM UTC-5 Chris Clawson wrote:
>
>> Follow-up - *Still not seeing images in viewer*, but the image 
>> metadata/etc now correctly shows up in the left bar of the viewer. The 
>> viewer now knows there are 9 images but the screen error says ' TypeError: 
>> NetworkError when attempting to fetch resource' .
>>  My earlier installation omitted an entry in 
>> /opt/dspace/config/modules/iiif.cfg, where I had "iiif.enabled = false". 
>> This somehow didn't seem to matter then but it does now. The current 
>> iiif.cfg file has the entry iiif.enabled = true.
>>
>> As of this writing, the console messages are saying things, like:
>> ERROR Error: unsafe value used in a resource URL context (see 
>> https://g.co/ng/security#xss)
>> ERROR TypeError: this.vcr is undefined
>> Uncaught TypeError: Jc.viewer(...) is not a function
>> and
>> Cross-Origin Request Blocked: The Same Origin Policy disallows reading 
>> the remote resource at 
>> http://localhost:8182/iiif/2/d884028d-4d4f-4b96-9568-59fb0533cef8/info.json. 
>> (Reason: CORS request did not succeed). Status code: (null).
>> (help?)
>>
>> On Tuesday, April 5, 2022 at 6:56:38 PM UTC-4 Chris Clawson wrote:
>>
>>> I am not sure what happened or where to investigate. I thought I had 
>>> correctly applied the 7.2.1 patch for the backend security update. 
>>> Everything seemed okay, except now I see that none of the 
>>> dspace.iiif.enabled items will display images in the Mirador viewer.
>>> The following item had been setup as a series of slides...
>>> https://meloware.org:8443/handle/123456789/6475 
>>> There were 9 images, each with an edited description in the individual 
>>> bitstreams metadata. Now the viewer says "1 of 0". 
>>>
>>> Before I begin to tear things apart, is there an issue here? First 
>>> suggestions?
>>>
>>

-- 
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/b003ba79-c95f-4ca7-ab52-7a497378db2an%40googlegroups.com.

[dspace-tech] Re: Broken Mirador/ iiif viewer with 7.2.1 patch?

[Chris Clawson]

Follow-up - *Still not seeing images in viewer*, but the image metadata/etc 
now correctly shows up in the left bar of the viewer. The viewer now knows 
there are 9 images but the screen error says ' TypeError: NetworkError when 
attempting to fetch resource' .
 My earlier installation omitted an entry in 
/opt/dspace/config/modules/iiif.cfg, where I had "iiif.enabled = false". 
This somehow didn't seem to matter then but it does now. The current 
iiif.cfg file has the entry iiif.enabled = true.

As of this writing, the console messages are saying things, like:
ERROR Error: unsafe value used in a resource URL context (see 
https://g.co/ng/security#xss)
ERROR TypeError: this.vcr is undefined
Uncaught TypeError: Jc.viewer(...) is not a function
and
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the 
remote resource at 
http://localhost:8182/iiif/2/d884028d-4d4f-4b96-9568-59fb0533cef8/info.json. 
(Reason: CORS request did not succeed). Status code: (null).
(help?)

On Tuesday, April 5, 2022 at 6:56:38 PM UTC-4 Chris Clawson wrote:

> I am not sure what happened or where to investigate. I thought I had 
> correctly applied the 7.2.1 patch for the backend security update. 
> Everything seemed okay, except now I see that none of the 
> dspace.iiif.enabled items will display images in the Mirador viewer.
> The following item had been setup as a series of slides...
> https://meloware.org:8443/handle/123456789/6475 
> There were 9 images, each with an edited description in the individual 
> bitstreams metadata. Now the viewer says "1 of 0". 
>
> Before I begin to tear things apart, is there an issue here? First 
> suggestions?
>

-- 
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/bfa20b61-66ef-45ef-9334-41abcd5en%40googlegroups.com.

[dspace-tech] Broken Mirador/ iiif viewer with 7.2.1 patch?

[Chris Clawson]

I am not sure what happened or where to investigate. I thought I had 
correctly applied the 7.2.1 patch for the backend security update. 
Everything seemed okay, except now I see that none of the 
dspace.iiif.enabled items will display images in the Mirador viewer.
The following item had been setup as a series of slides...
https://meloware.org:8443/handle/123456789/6475 
There were 9 images, each with an edited description in the individual 
bitstreams metadata. Now the viewer says "1 of 0". 

Before I begin to tear things apart, is there an issue here? First 
suggestions?

-- 
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/8c224098-056a-4360-81b3-2c5c6b8f9c1dn%40googlegroups.com.

[dspace-tech] Unable to view Usage Statistics in 7.2

[Chris Clawson]

 

Please help fix my solr statistics. I am running DS 7.2 on a web server and 
you can see it at https://meloware.org:8443/home

The Statistics pages are empty, even logged in as Administrator.

Home Page: No data available 

Community Total Visits: 'this' community 0

Item Total Visits: 'this' item 0

I am unable to find my solr usage data. Where should it be? I found nothing 
in:

/var/solr/data/statistics

I don't know where to go at this point, so please help.

-- 
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/bb79bc21-bff0-42f6-965e-83505cd83a87n%40googlegroups.com.

[dspace-tech] Re: Trouble exporting AIP in 7.2

[Chris Clawson]

Found the problem! It is explained in the earlier thread " Restoring a 
deleted collection ". My dspace.cfg defines a temporary "upload" directory 
as "upload.temp.dir", but this folder was not created during my 
installation. I manually added this folder and gave it the same group:owner 
as the home dspace directory. These problem AIP commands now work. I 
suggest that this point gets included in the documentation.

On Friday, March 11, 2022 at 10:20:02 AM UTC-5 Chris Clawson wrote:

> I am attempting to create and restore AIP backups from the command line in 
> my DSpace 7.2 installation. I seem to be able to do this with my DS 6.3 
> installation, but am only able to export and import single items to 7.2. 
> Please show me where I am going wrong...
>
> The version 7.2 export session fails and produces a zipfile of size zero. 
> The session is pasted below and provides no clue of what file or directory 
> it can't see. I am trying to follow exactly what the documentation 
> instructs. It works with DSpace 6.3, but not in this install of 7.2. Any 
> suggestions? Thanks.
>
> root@melo4:/home/backup-h# /opt/dspace/bin/dspace packager -d -a -t AIP -e 
> xx...@x.org -i 123456789/32 aip32.zip
>
>
> Disseminating DSpace COMMUNITY [ hdl=123456789/32 ] to aip32.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.base/java.io.UnixFileSystem.createFileExclusively(Native Method)
>
> at java.base/java.io.File.createTempFile(File.java:2129)
>
> at 
> org.dspace.content.crosswalk.RoleCrosswalk.disseminateElement(RoleCrosswalk.java:189)
>
> at 
> org.dspace.content.packager.AbstractMETSDisseminator.crosswalkToMetsElement(AbstractMETSDisseminator.java:1264)
>
> at 
> org.dspace.content.packager.AbstractMETSDisseminator.makeMdSec(AbstractMETSDisseminator.java:606)
>
> at 
> org.dspace.content.packager.AbstractMETSDisseminator.addToAmdSec(AbstractMETSDisseminator.java:700)
>
> at 
> org.dspace.content.packager.AbstractMETSDisseminator.addAmdSec(AbstractMETSDisseminator.java:725)
>
> at 
> org.dspace.content.packager.AbstractMETSDisseminator.makeManifest(AbstractMETSDisseminator.java:814)
>
> at 
> org.dspace.content.packager.AbstractMETSDisseminator.writeZipPackage(AbstractMETSDisseminator.java:328)
>
> at 
> org.dspace.content.packager.AbstractMETSDisseminator.disseminate(AbstractMETSDisseminator.java:264)
>
> at 
> org.dspace.content.packager.DSpaceAIPDisseminator.disseminate(DSpaceAIPDisseminator.java:160)
>
> at 
> org.dspace.content.packager.AbstractPackageDisseminator.disseminateAll(AbstractPackageDisseminator.java:100)
>
> at org.dspace.app.packager.Packager.disseminate(Packager.java:604)
>
> at org.dspace.app.packager.Packager.main(Packager.java:439)
>
> 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)
>
> root@melo4:/home/backup-h#
>

-- 
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/1d601a2b-8701-4407-9ccf-65c7e587bce3n%40googlegroups.com.

[dspace-tech] Trouble exporting AIP in 7.2

[Chris Clawson]

 

I am attempting to create and restore AIP backups from the command line in 
my DSpace 7.2 installation. I seem to be able to do this with my DS 6.3 
installation, but am only able to export and import single items to 7.2. 
Please show me where I am going wrong...

The version 7.2 export session fails and produces a zipfile of size zero. 
The session is pasted below and provides no clue of what file or directory 
it can't see. I am trying to follow exactly what the documentation 
instructs. It works with DSpace 6.3, but not in this install of 7.2. Any 
suggestions? Thanks.

root@melo4:/home/backup-h# /opt/dspace/bin/dspace packager -d -a -t AIP -e 
xx...@x.org -i 123456789/32 aip32.zip


Disseminating DSpace COMMUNITY [ hdl=123456789/32 ] to aip32.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.base/java.io.UnixFileSystem.createFileExclusively(Native Method)

at java.base/java.io.File.createTempFile(File.java:2129)

at 
org.dspace.content.crosswalk.RoleCrosswalk.disseminateElement(RoleCrosswalk.java:189)

at 
org.dspace.content.packager.AbstractMETSDisseminator.crosswalkToMetsElement(AbstractMETSDisseminator.java:1264)

at 
org.dspace.content.packager.AbstractMETSDisseminator.makeMdSec(AbstractMETSDisseminator.java:606)

at 
org.dspace.content.packager.AbstractMETSDisseminator.addToAmdSec(AbstractMETSDisseminator.java:700)

at 
org.dspace.content.packager.AbstractMETSDisseminator.addAmdSec(AbstractMETSDisseminator.java:725)

at 
org.dspace.content.packager.AbstractMETSDisseminator.makeManifest(AbstractMETSDisseminator.java:814)

at 
org.dspace.content.packager.AbstractMETSDisseminator.writeZipPackage(AbstractMETSDisseminator.java:328)

at 
org.dspace.content.packager.AbstractMETSDisseminator.disseminate(AbstractMETSDisseminator.java:264)

at 
org.dspace.content.packager.DSpaceAIPDisseminator.disseminate(DSpaceAIPDisseminator.java:160)

at 
org.dspace.content.packager.AbstractPackageDisseminator.disseminateAll(AbstractPackageDisseminator.java:100)

at org.dspace.app.packager.Packager.disseminate(Packager.java:604)

at org.dspace.app.packager.Packager.main(Packager.java:439)

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)

root@melo4:/home/backup-h#

-- 
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/3163b097-fa21-4e31-912d-0485b9c26823n%40googlegroups.com.

[dspace-tech] How to enable IIIF for item in 7.2?

[Chris Clawson]

How is an items bitstreams enabled for iiif in 7.2?
If I attempt to edit the item metadata, and add the field  
"dspace.​iiif.​enabled", 
it is red lined and I am told to enter a valid value. 

-- 
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/f0772285-a4aa-4981-bbcc-b177a4cdebb5n%40googlegroups.com.

[dspace-tech] Re: How to migrate your UI Configurations to YAML ?

[Chris Clawson]

WARNING - My method of using the relative paths to the earlier DS 7.1 
directory did run under the yarn env:yaml  script, but it did not produce a 
useful config.prod.yml file. Angular insisted on listening at 
localhost:8080, rather than localhost:4000. I don't know why this didn't 
work, but Mohammad's suggestion of editing the config.example.yml to define 
my URLs and ports worked much better and easier.

On Wednesday, February 9, 2022 at 2:15:00 AM UTC-5 alo...@gmail.com wrote:

> On Wednesday, February 9, 2022 at 2:47:08 AM UTC+3 Chris Clawson wrote:
>
>> Everything seemed to finish well, although a full system reboot failed 
>> to start angular as a service. I guess this is my last barrier to a 
>> functional upgrade, but it is the stuff of a new thread if I need help.
>>
>  
> You need to replace the ExecStart line in the service startup script as 
> you see below and you also need to change the WorkingDirectory path to 
> reflect the new path if it's changed.
> vi /lib/systemd/system/dspace-angular.service
> ExecStart=/usr/bin/node dist/server/main
> WorkingDirectory=/opt/dspace-angular
>

-- 
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/90d07c77-22cb-4df5-8f5a-a25756a19d34n%40googlegroups.com.

[dspace-tech] Re: How to migrate your UI Configurations to YAML ?

[Chris Clawson]

Thank you. Yes, it is a bit awkward. 
I kept and renamed my 7.1 angular directory and properly referenced  
"environment.prod.ts" in the yarn command. I moved the new config.prod.yml 
to it's proper place and ran the " yarn run build:prod" command to build 
the final production version.
I will later delete my old version directories. 

Everything seemed to finish well, although a full system reboot failed to 
start angular as a service. I guess this is my last barrier to a functional 
upgrade, but it is the stuff of a new thread if I need help.
Again - I appreciate the support and am happy to help ring out the new 
version.

On Tuesday, February 8, 2022 at 5:58:07 PM UTC-5 Tim Donohue wrote:

> Hi Chris,
>
> You are 100% correct.  It looks like during 7.2 development, after we 
> created the "yarn env:yaml" script, we then moved some code around, and 
> broke those imports at the top of the old "environment.prod.ts".   So, if 
> you copy it over into the 7.2 directory structure, it won't work because 
> those imports are broken.
>
> Currently, it appears there are two options:
> 1) If your 7.1 folder is separate for the 7.2 folder, you could keep 
> "environment.prod.ts" in the 7.1 directories, and *reference it* from the 
> 7.2 folder.  It'd be a little odd, but look kinda like this. You'd run this 
> from 7.2 root folder.
>
> yarn env:yaml ../../dspace-7.1-old/src/environments/environment.prod.ts 
> config/config.prod.yml
>
> 2) Or, if you want to copy your environment.prod.ts into the 7.2 
> directories first (or don't have the old 7.1 code handy), then do this:
>
> Remove/comment out all 4 existing imports in `environment.prod.ts`.  
> Replace them with these lines at the top of that file. (With those 4 
> imports removed, You need 4 objects, all of which are fully defined below)
>
> interface GlobalConfig { }
>
> enum NotificationAnimationsType {
> Fade = 'fade',
> FromTop = 'fromTop',
> FromRight = 'fromRight',
> FromBottom = 'fromBottom',
> FromLeft = 'fromLeft',
> Rotate = 'rotate',
> Scale = 'scale'
>   }
>
> enum BrowseByType {
> Title = 'title',
> Metadata = 'metadata',
> Date = 'date'
> }
>
> enum RestRequestMethod {
> GET = 'GET',
> POST = 'POST',
> PUT = 'PUT',
> DELETE = 'DELETE',
> OPTIONS = 'OPTIONS',
> HEAD = 'HEAD',
> PATCH = 'PATCH'
> }
>
> If you have those imports commented out, and replaced with those lines, 
> then the "environment.prod.ts" can be placed *anywhere* (as it no longer 
> has imports) and the "yarn env:yaml" command can be pointed at it wherever 
> it sits.
>
> I'll get this all moved over into our official docs, as this is obviously 
> more complex then I initially thought...but I'm glad you've helped us 
> discover the issue.
>
> Tim
>
> On Tuesday, February 8, 2022 at 4:18:19 PM UTC-6 Chris Clawson wrote:
>
>> Still doesn't work and I think I know why. The environment.prod.ts file 
>> declares 4 files to import, so the script is unable to find them if  
>> environment.prod.ts is placed in some arbitrary location under the DSpace 
>> 7.2 angular root directory. Shall I presume that these import paths  need 
>> to point to the earlier, DSpace 7.1 files? I guess I may eventually figure 
>> it out. Unless I hear different, I suppose I need to modify 
>> environment.prod.ts to correctly point to these other 4 files:
>> ../config/global-config.interface
>> ../app/shared/notifications/models/notification-animations-type
>> ../app/browse-by/browse-by-switcher/browse-by-decorator
>> ../app/core/data/rest-request-method
>> On Tuesday, February 8, 2022 at 3:54:58 PM UTC-5 Tim Donohue wrote:
>>
>>> Hi Chris,
>>>
>>> It sounds like our the docs need clarifying here.  You need to run `yarn 
>>> env:yaml` from the *NEW 7.2 codebase directory*.  Since you are trying to 
>>> run it from your old 7.1 code, it is throwing an error as that command 
>>> didn't exist in the 7.1 codebase.
>>>
>>> So, the docs were written assuming you were going to essentially install 
>>> 7.2 "on top of" 7.1.  In that situation, you'd have the 7.2 code...but your 
>>> old 7.1 "environment.prod.ts" would still be around (as the update to 7.2 
>>> doesn't delete that file).
>>>
>>> For your purposes, it sounds like your 7.2 code *is in a separate 
>>> directory from 7.1 code*.  So, for your purposes, do this:
>>> 1. Copy the "src/environment/environment.prod.ts" from your 7.1 (old) 
>>> directory, over into the 7.2 (new) directory. 

[dspace-tech] Re: How to migrate your UI Configurations to YAML ?

[Chris Clawson]

Ouch!
These 4 imports in environment.prod.ts, in turn refer to all sorts of other 
.ts files from the old installation. It is not as simple as copying four 
files over, in addition to environment.prod.ts and place under the DSpace 
7.2 angular code root.

Okay - From the DSpace 7.2 angular root directory this following command 
produced a config.prod.ts file in the same root directory:
yarn env:yaml ..//dspace-angular-old/src/environments/environment.prod.ts 
config.prod.yml

So, all I need is to move this to the [angular-root]/config directory and 
then :
yarn run build:prod
?


On Tuesday, February 8, 2022 at 5:18:19 PM UTC-5 Chris Clawson wrote:

> Still doesn't work and I think I know why. The environment.prod.ts file 
> declares 4 files to import, so the script is unable to find them if  
> environment.prod.ts is placed in some arbitrary location under the DSpace 
> 7.2 angular root directory. Shall I presume that these import paths  need 
> to point to the earlier, DSpace 7.1 files? I guess I may eventually figure 
> it out. Unless I hear different, I suppose I need to modify 
> environment.prod.ts to correctly point to these other 4 files:
> ../config/global-config.interface
> ../app/shared/notifications/models/notification-animations-type
> ../app/browse-by/browse-by-switcher/browse-by-decorator
> ../app/core/data/rest-request-method
> On Tuesday, February 8, 2022 at 3:54:58 PM UTC-5 Tim Donohue wrote:
>
>> Hi Chris,
>>
>> It sounds like our the docs need clarifying here.  You need to run `yarn 
>> env:yaml` from the *NEW 7.2 codebase directory*.  Since you are trying to 
>> run it from your old 7.1 code, it is throwing an error as that command 
>> didn't exist in the 7.1 codebase.
>>
>> So, the docs were written assuming you were going to essentially install 
>> 7.2 "on top of" 7.1.  In that situation, you'd have the 7.2 code...but your 
>> old 7.1 "environment.prod.ts" would still be around (as the update to 7.2 
>> doesn't delete that file).
>>
>> For your purposes, it sounds like your 7.2 code *is in a separate 
>> directory from 7.1 code*.  So, for your purposes, do this:
>> 1. Copy the "src/environment/environment.prod.ts" from your 7.1 (old) 
>> directory, over into the 7.2 (new) directory.  Where you choose to copy it 
>> into doesn't really matter, but you could put it under "[src-7.2]/config", 
>> where the configs eventually need to be.
>> 2. Now, go to [src-7.2] (root 7.2 directory) and run:  "yarn env:yaml 
>> config/environment.prod.ts config/config.prod.yml".   
>>
>> That should be it.  You can then look at that config/config.prod.yml to 
>> double check it looks correct (the same settings exist in both the YAML and 
>> TS config files, they just have a different syntax).  Once you are 
>> satisfied, you can delete the "environment.prod.ts" from your 
>> [src-7.2]/config/ folder.  It's not used in 7.2 at all.
>>
>> Tim
>>
>>
>>
>> On Tuesday, February 8, 2022 at 12:26:12 PM UTC-6 Chris Clawson wrote:
>>
>>> Thanks, Tim, but still frustrated!
>>> I understand you are saying to go to my old /src/environments directory, 
>>> and run this command:
>>> yarn env:yaml environment.prod.ts
>>> Here is the response I get:
>>> root@melo4:/opt/dspace-angular-old/src/environments# yarn env:yaml 
>>> environment.prod.ts
>>> yarn run v1.22.17
>>> error Command "env:yaml" not found.
>>>
>>> -- embarrassing, did I break something?
>>> On Tuesday, February 8, 2022 at 12:55:19 PM UTC-5 Tim Donohue wrote:
>>>
>>>> Hi Chris,
>>>>
>>>> That "yarn env:yaml" command only requires one input, whish is your old 
>>>> "environment.*.ts" file.  So, that second input is *optional*.  If you 
>>>> only 
>>>> give it one input, it'll write the output YAML file into that same 
>>>> directory.  That's perfectly ok...you'd just want to eventually ensure 
>>>> that 
>>>> YAML file gets moved over into 
>>>> /opt/dspace-angular-dspace/config/config.prod.yml , which is where the UI 
>>>> will look for your configs in 7.2 (and above).
>>>>
>>>> So, I would recommend trying the script with a single input, if the 
>>>> multiple inputs is getting confusing.
>>>>
>>>> If somehow the script is erroring out or not working at all, send the 
>>>> error message to this list and we'll take a closer look at it.   
>>>>
>>>> If worst came to worst, you also can just recre

[dspace-tech] Re: How to migrate your UI Configurations to YAML ?

[Chris Clawson]

Ouch! 
These 4 imports in environment.prod.ts, in turn refer to all sorts of other 
.ts files from the old installation. It is not as simple as copying four 
files over, in addition to environment.prod.ts and place under the DSpace 
7.2 angular code root.

Okay - From the DSpace 7.2 angular root directory this following command 
produced a config.prod.ts file in the same root directory:
yarn env:yaml ..//dspace-angular-old/src/environments/environment.prod.ts 
config.prod.ts

So, all I need is to move this to the [angular-root]/config directory and 
then :
yarn run build:prod 
?
On Tuesday, February 8, 2022 at 5:18:19 PM UTC-5 Chris Clawson wrote:

> Still doesn't work and I think I know why. The environment.prod.ts file 
> declares 4 files to import, so the script is unable to find them if  
> environment.prod.ts is placed in some arbitrary location under the DSpace 
> 7.2 angular root directory. Shall I presume that these import paths  need 
> to point to the earlier, DSpace 7.1 files? I guess I may eventually figure 
> it out. Unless I hear different, I suppose I need to modify 
> environment.prod.ts to correctly point to these other 4 files:
> ../config/global-config.interface
> ../app/shared/notifications/models/notification-animations-type
> ../app/browse-by/browse-by-switcher/browse-by-decorator
> ../app/core/data/rest-request-method
> On Tuesday, February 8, 2022 at 3:54:58 PM UTC-5 Tim Donohue wrote:
>
>> Hi Chris,
>>
>> It sounds like our the docs need clarifying here.  You need to run `yarn 
>> env:yaml` from the *NEW 7.2 codebase directory*.  Since you are trying to 
>> run it from your old 7.1 code, it is throwing an error as that command 
>> didn't exist in the 7.1 codebase.
>>
>> So, the docs were written assuming you were going to essentially install 
>> 7.2 "on top of" 7.1.  In that situation, you'd have the 7.2 code...but your 
>> old 7.1 "environment.prod.ts" would still be around (as the update to 7.2 
>> doesn't delete that file).
>>
>> For your purposes, it sounds like your 7.2 code *is in a separate 
>> directory from 7.1 code*.  So, for your purposes, do this:
>> 1. Copy the "src/environment/environment.prod.ts" from your 7.1 (old) 
>> directory, over into the 7.2 (new) directory.  Where you choose to copy it 
>> into doesn't really matter, but you could put it under "[src-7.2]/config", 
>> where the configs eventually need to be.
>> 2. Now, go to [src-7.2] (root 7.2 directory) and run:  "yarn env:yaml 
>> config/environment.prod.ts config/config.prod.yml".   
>>
>> That should be it.  You can then look at that config/config.prod.yml to 
>> double check it looks correct (the same settings exist in both the YAML and 
>> TS config files, they just have a different syntax).  Once you are 
>> satisfied, you can delete the "environment.prod.ts" from your 
>> [src-7.2]/config/ folder.  It's not used in 7.2 at all.
>>
>> Tim
>>
>>
>>
>> On Tuesday, February 8, 2022 at 12:26:12 PM UTC-6 Chris Clawson wrote:
>>
>>> Thanks, Tim, but still frustrated!
>>> I understand you are saying to go to my old /src/environments directory, 
>>> and run this command:
>>> yarn env:yaml environment.prod.ts
>>> Here is the response I get:
>>> root@melo4:/opt/dspace-angular-old/src/environments# yarn env:yaml 
>>> environment.prod.ts
>>> yarn run v1.22.17
>>> error Command "env:yaml" not found.
>>>
>>> -- embarrassing, did I break something?
>>> On Tuesday, February 8, 2022 at 12:55:19 PM UTC-5 Tim Donohue wrote:
>>>
>>>> Hi Chris,
>>>>
>>>> That "yarn env:yaml" command only requires one input, whish is your old 
>>>> "environment.*.ts" file.  So, that second input is *optional*.  If you 
>>>> only 
>>>> give it one input, it'll write the output YAML file into that same 
>>>> directory.  That's perfectly ok...you'd just want to eventually ensure 
>>>> that 
>>>> YAML file gets moved over into 
>>>> /opt/dspace-angular-dspace/config/config.prod.yml , which is where the UI 
>>>> will look for your configs in 7.2 (and above).
>>>>
>>>> So, I would recommend trying the script with a single input, if the 
>>>> multiple inputs is getting confusing.
>>>>
>>>> If somehow the script is erroring out or not working at all, send the 
>>>> error message to this list and we'll take a closer look at it.   
>>>>
>>>> If worst came to worst, you also can just recre

[dspace-tech] Re: How to migrate your UI Configurations to YAML ?

[Chris Clawson]

Still doesn't work and I think I know why. The environment.prod.ts file 
declares 4 files to import, so the script is unable to find them if  
environment.prod.ts is placed in some arbitrary location under the DSpace 
7.2 angular root directory. Shall I presume that these import paths  need 
to point to the earlier, DSpace 7.1 files? I guess I may eventually figure 
it out. Unless I hear different, I suppose I need to modify 
environment.prod.ts to correctly point to these other 4 files:
../config/global-config.interface
../app/shared/notifications/models/notification-animations-type
../app/browse-by/browse-by-switcher/browse-by-decorator
../app/core/data/rest-request-method
On Tuesday, February 8, 2022 at 3:54:58 PM UTC-5 Tim Donohue wrote:

> Hi Chris,
>
> It sounds like our the docs need clarifying here.  You need to run `yarn 
> env:yaml` from the *NEW 7.2 codebase directory*.  Since you are trying to 
> run it from your old 7.1 code, it is throwing an error as that command 
> didn't exist in the 7.1 codebase.
>
> So, the docs were written assuming you were going to essentially install 
> 7.2 "on top of" 7.1.  In that situation, you'd have the 7.2 code...but your 
> old 7.1 "environment.prod.ts" would still be around (as the update to 7.2 
> doesn't delete that file).
>
> For your purposes, it sounds like your 7.2 code *is in a separate 
> directory from 7.1 code*.  So, for your purposes, do this:
> 1. Copy the "src/environment/environment.prod.ts" from your 7.1 (old) 
> directory, over into the 7.2 (new) directory.  Where you choose to copy it 
> into doesn't really matter, but you could put it under "[src-7.2]/config", 
> where the configs eventually need to be.
> 2. Now, go to [src-7.2] (root 7.2 directory) and run:  "yarn env:yaml 
> config/environment.prod.ts config/config.prod.yml".   
>
> That should be it.  You can then look at that config/config.prod.yml to 
> double check it looks correct (the same settings exist in both the YAML and 
> TS config files, they just have a different syntax).  Once you are 
> satisfied, you can delete the "environment.prod.ts" from your 
> [src-7.2]/config/ folder.  It's not used in 7.2 at all.
>
> Tim
>
>
>
> On Tuesday, February 8, 2022 at 12:26:12 PM UTC-6 Chris Clawson wrote:
>
>> Thanks, Tim, but still frustrated!
>> I understand you are saying to go to my old /src/environments directory, 
>> and run this command:
>> yarn env:yaml environment.prod.ts
>> Here is the response I get:
>> root@melo4:/opt/dspace-angular-old/src/environments# yarn env:yaml 
>> environment.prod.ts
>> yarn run v1.22.17
>> error Command "env:yaml" not found.
>>
>> -- embarrassing, did I break something?
>> On Tuesday, February 8, 2022 at 12:55:19 PM UTC-5 Tim Donohue wrote:
>>
>>> Hi Chris,
>>>
>>> That "yarn env:yaml" command only requires one input, whish is your old 
>>> "environment.*.ts" file.  So, that second input is *optional*.  If you only 
>>> give it one input, it'll write the output YAML file into that same 
>>> directory.  That's perfectly ok...you'd just want to eventually ensure that 
>>> YAML file gets moved over into 
>>> /opt/dspace-angular-dspace/config/config.prod.yml , which is where the UI 
>>> will look for your configs in 7.2 (and above).
>>>
>>> So, I would recommend trying the script with a single input, if the 
>>> multiple inputs is getting confusing.
>>>
>>> If somehow the script is erroring out or not working at all, send the 
>>> error message to this list and we'll take a closer look at it.   
>>>
>>> If worst came to worst, you also can just recreate your configs in YAML 
>>> (based on the examples in config.example.yml) ... but, I completely 
>>> understand that it's a ton easier to just migrate the settings over.
>>>
>>> Tim
>>>
>>> On Tuesday, February 8, 2022 at 9:44:46 AM UTC-6 Chris Clawson wrote:
>>>
>>>> Upgrading DSpace 7.x (7.1 to 7.2), upgrading the Front-end, step 'C' 
>>>> says I should use yarn to convert the earlier installation's .ts files to 
>>>> .yml. I am not able to get past this step. Perhaps I only need some 
>>>> assistance in the specific grammar in using the conversion script.
>>>>
>>>> The path to my my old DSpace 7.1 angular 'environments' directory
>>>>
>>>> /opt/dspace-angular-old/src/environments
>>>>
>>>> My unzipped DSpace 7.2 angular is at:
>>>>
>>>> /opt/dspace-angular-dspace
>>>>
>&g

[dspace-tech] Re: How to migrate your UI Configurations to YAML ?

[Chris Clawson]

Thanks, Tim, but still frustrated!
I understand you are saying to go to my old /src/environments directory, 
and run this command:
yarn env:yaml environment.prod.ts
Here is the response I get:
root@melo4:/opt/dspace-angular-old/src/environments# yarn env:yaml 
environment.prod.ts
yarn run v1.22.17
error Command "env:yaml" not found.

-- embarrassing, did I break something?
On Tuesday, February 8, 2022 at 12:55:19 PM UTC-5 Tim Donohue wrote:

> Hi Chris,
>
> That "yarn env:yaml" command only requires one input, whish is your old 
> "environment.*.ts" file.  So, that second input is *optional*.  If you only 
> give it one input, it'll write the output YAML file into that same 
> directory.  That's perfectly ok...you'd just want to eventually ensure that 
> YAML file gets moved over into 
> /opt/dspace-angular-dspace/config/config.prod.yml , which is where the UI 
> will look for your configs in 7.2 (and above).
>
> So, I would recommend trying the script with a single input, if the 
> multiple inputs is getting confusing.
>
> If somehow the script is erroring out or not working at all, send the 
> error message to this list and we'll take a closer look at it.   
>
> If worst came to worst, you also can just recreate your configs in YAML 
> (based on the examples in config.example.yml) ... but, I completely 
> understand that it's a ton easier to just migrate the settings over.
>
> Tim
>
> On Tuesday, February 8, 2022 at 9:44:46 AM UTC-6 Chris Clawson wrote:
>
>> Upgrading DSpace 7.x (7.1 to 7.2), upgrading the Front-end, step 'C' says 
>> I should use yarn to convert the earlier installation's .ts files to .yml. 
>> I am not able to get past this step. Perhaps I only need some assistance in 
>> the specific grammar in using the conversion script.
>>
>> The path to my my old DSpace 7.1 angular 'environments' directory
>>
>> /opt/dspace-angular-old/src/environments
>>
>> My unzipped DSpace 7.2 angular is at:
>>
>> /opt/dspace-angular-dspace
>>
>> My command prompt is located at /opt/dspace-angular-dspace/config
>>
>> Given these conditions, *would someone please provide me* with a 
>> specific example of how to produce a working command for the this 
>> documentation example to convert environment.prod.ts
>>
>> yarn env:yaml src/environments/environment.prod.ts config/config.prod.yml 
>>
>

-- 
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/46325d52-4e0a-4700-8cba-11909b06819bn%40googlegroups.com.

[dspace-tech] How to migrate your UI Configurations to YAML ?

[Chris Clawson]

 

Upgrading DSpace 7.x (7.1 to 7.2), upgrading the Front-end, step 'C' says I 
should use yarn to convert the earlier installation's .ts files to .yml. I 
am not able to get past this step. Perhaps I only need some assistance in 
the specific grammar in using the conversion script.

The path to my my old DSpace 7.1 angular 'environments' directory

/opt/dspace-angular-old/src/environments

My unzipped DSpace 7.2 angular is at:

/opt/dspace-angular-dspace

My command prompt is located at /opt/dspace-angular-dspace/config

Given these conditions, *would someone please provide me* with a specific 
example of how to produce a working command for the this documentation 
example to convert environment.prod.ts

yarn env:yaml src/environments/environment.prod.ts config/config.prod.yml 

-- 
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/408d372b-3f65-4bf4-9288-a56233e5e950n%40googlegroups.com.

[dspace-tech] Re: Cantaloupe and Mirador setup help, Please

[Chris Clawson]

Solid advice and now I have working features! I was unable to find critical 
details for my setup until Mohammad took the time to explain the detail and 
provide specific, working examples. Thank you so much for the help and I 
recommend any DSpace users that encounter problems to consult this forum 
and ask detailed and specific questions. Be sure all the context and detail 
is included. In the case of this thread, Mohammad not only explained what I 
needed, but he edited and provided the configuration files specific to my 
system!  This is an important service! Thanks to all the Developers, 
Mohammad, and all the others who have helped me in the past.
Chris

On Monday, January 31, 2022 at 12:12:06 AM UTC-5 alo...@gmail.com wrote:

> Sorry to see you still facing an issue with the image server. Just follow 
> the steps to get it working. I had to separate the virtual hosting config 
> files because (a) Frontend reverse-proxy settings conflicts with the image 
> server setting (b) To save you some bucks buying a newer certificate.
>
> *You need to drop the attached apache config virtual hosts config files 
> into /etc/apache2/sites-available/*
>
> *# You also need to add a newer port (444) as you see it below.*
> *vi /etc/apache2/ports.conf*
> 
> Listen 443 https
> Listen 444 https
> Listen 8443 https
>
> *# Enable the new virtual site*
> a2ensite img.conf
>
> *# Open port 444 in the firewall if you have the default ufw firewall 
> enabled and running.*
> ufw allow 444
>
> *# Restart the Apache webserver*
> systemctl restart apache2
>
> *# In cantaloupe.properties configuration file you need to set the 
> following configuration options as you see them:*
> http.enabled = true
> http.host = localhost
> http.port = 8182
> endpoint.admin.enabled = true
> endpoint.admin.username = SET-THE-ADMIN-USERNAME-HERE
> endpoint.admin.secret = SET-A-SECURE-PASSWORD-HERE
> source.static = HttpSource
> HttpSource.BasicLookupStrategy.url_prefix = 
> https://meloware.org:8443/server/api/core/bitstreams/
> HttpSource.BasicLookupStrategy.url_suffix = /content
>
>
> *# In /opt/dspace/config/modules/iiif.cfg :*
> iiif.enabled = true
> iiif.image.server = https://meloware.org:444/iiif/2/
>
>
>
> Let me know if you still need help with it & Check Omeka it's possible it 
> fits your need. 
> https://omeka.org/classic/docs/GettingStarted/UsingOmeka/#how-are-others-using-omeka-classic
> On Sunday, January 30, 2022 at 3:48:42 AM UTC+3 Chris Clawson wrote:
>
>> I have been struggling for days to get IIIF support running in my DSpace 
>> 7, with Mirador and Cantaloupe. This following link shows how far I got: 
>>
>> https://meloware.org:8443/handle/123456789/19
>>
>> There are several images in this item and the Mirador viewer seems able 
>> to recover the image metadata, but is encountering a network error when 
>> trying to retrieve the actual images. This item has the metadata field 
>> dspace.iiif.enabled added and set to 'true'. The error message is 
>> “TypeError: NetworkError when attempting to fetch resource. “
>>
>> I could use some help at this point as to why these images aren't being 
>> displayed.
>>
>> This is a server container running Ubuntu 20.04. Apache2 has an open port 
>> (443) which is a Virtual Host to Wordpress. This is controlled by the 
>> /etc/apache2/sites-available “wordpress.conf”. The Virtual Host file 
>> “dspace.conf” uses port 8443 to reach Dspace 7 and 8183 to talk to 
>> Cantaloupe. My problem may be here, but I am tired of guessing.
>>
>> Other important config files are also included. I can always provide more 
>> info, if asked.
>>
>

-- 
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/c749b051-d1a1-4691-9913-be3391314f13n%40googlegroups.com.

[dspace-tech] Cantaloupe and Mirador setup help, Please

[Chris Clawson]

 

I have been struggling for days to get IIIF support running in my DSpace 7, 
with Mirador and Cantaloupe. This following link shows how far I got: 

https://meloware.org:8443/handle/123456789/19

There are several images in this item and the Mirador viewer seems able to 
recover the image metadata, but is encountering a network error when trying 
to retrieve the actual images. This item has the metadata field 
dspace.iiif.enabled added and set to 'true'. The error message is 
“TypeError: NetworkError when attempting to fetch resource. “

I could use some help at this point as to why these images aren't being 
displayed.

This is a server container running Ubuntu 20.04. Apache2 has an open port 
(443) which is a Virtual Host to Wordpress. This is controlled by the 
/etc/apache2/sites-available “wordpress.conf”. The Virtual Host file 
“dspace.conf” uses port 8443 to reach Dspace 7 and 8183 to talk to 
Cantaloupe. My problem may be here, but I am tired of guessing.

Other important config files are also included. I can always provide more 
info, if asked.

-- 
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/2cd1f560-c917-4db0-93fa-b3650eecefb7n%40googlegroups.com.

 ServerName meloware.org
 LogLevel warn
 ErrorLog ${APACHE_LOG_DIR}/meloware.org.error.log
 CustomLog ${APACHE_LOG_DIR}/meloware.org.access.log combined
 ProxyRequests On
 SSLEngine on
 SSLProxyEngine on
 SSLCertificateFile /etc/apache2/ssl/meloware_org.crt
 SSLCertificateKeyFile /etc/apache2/ssl/meloware_org.pem
 SSLCertificateChainFile /etc/apache2/ssl/meloware_org.ca-bundle
 SSLCompression off
 ProxyPreserveHost on
 SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1
 SSLCipherSuite  
ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
 SSLHonorCipherOrder off
 SSLSessionTickets   off
 ProxyPreserveHost On
 RequestHeader set X-Forwarded-Proto "https"

   
   AddDefaultCharset Off
   Require all granted
   

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




 ServerName meloware.org
 LogLevel warn
 ErrorLog ${APACHE_LOG_DIR}/meloware.org.error.log
 CustomLog ${APACHE_LOG_DIR}/meloware.org.access.log combined
 ProxyRequests On
 SSLEngine on
 SSLProxyEngine on
 SSLCertificateFile /etc/apache2/ssl/meloware_org.crt
 SSLCertificateKeyFile /etc/apache2/ssl/meloware_org.pem
 SSLCertificateChainFile /etc/apache2/ssl/meloware_org.ca-bundle
 SSLCompression off
 ProxyPreserveHost on
 SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1
 SSLCipherSuite  
ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
 SSLHonorCipherOrder off
 SSLSessionTickets   off
 ProxyPreserveHost On
 RequestHeader set X-Forwarded-Proto "https"

   
   AddDefaultCharset Off
   Require all granted
   

 ProxyPass / http://localhost:8182/
 ProxyPassReverse / http://localhost:8182/





 ServerName meloware.org
 LogLevel warn
 ErrorLog ${APACHE_LOG_DIR}/meloware.org.error.log
 CustomLog ${APACHE_LOG_DIR}/meloware.org.access.log combined

 ProxyPass / http://localhost:8182/
 ProxyPassReverse / http://localhost:8182/




 ServerName meloware.org
 Redirect / https://meloware.org



 ServerName meloware.org
 DocumentRoot /var/www/html
 LogLevel warn
 ErrorLog ${APACHE_LOG_DIR}/meloware.org.error.log
 CustomLog ${APACHE_LOG_DIR}/meloware.org.access.log combined
 SSLEngine on
 SSLCertificateFile /etc/apache2/ssl/meloware_org.crt
 SSLCertificateKeyFile /etc/apache2/ssl/meloware_org.pem
 SSLCertificateChainFile /etc/apache2/ssl/meloware_org.ca-bundle
 SSLCompression off
 ProxyPreserveHost on
 SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1
 SSLCipherSuite  
ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
 SSLHonorCipherOrder off
 

[dspace-tech] Presenting multiple descriptions in DSpace 7

[Chris Clawson]

Our DSpace 6 site would use multiple descriptions about an item to appear 
as paragraphs in the item view. It is very desirable for us to present 
several descriptions in this way, especially if each focuses on a different 
aspect of the item being described.

DSpace 7 still allows me to include multiple 'dc.description' fields to an 
item, but there is now no clear paragraph break presented as I had enjoyed 
before in the DSpace item view. Is there a way to get this behavior back or 
might it get included in a future release?

-- 
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/b8fa6b30-ab25-450a-aeb5-94be5e9342b2n%40googlegroups.com.

[dspace-tech] Item bitstream viewing in DSpace 7

[Chris Clawson]

 

Things have changed in DSpace 7's item view. In 6.3, an item view displayed 
a thumbnail (with an embedded link) as well as a text “View/Open link”. 
Clicking on either would open the bitstream into the current browser 
window. Now in 7, the embedded link inside the thumbnail is gone and the 
“Files” link will only initiate a download dialog.

Is there a setting available to revert to the old behavior? Image oriented 
repository users may not wish to download each and every bitstream, 
especially before first seeing exactly what it looks like. If this is not 
possible now, will it be in the future? (Please?)

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

Re: [dspace-tech] Using PHP for DSpace content in Wordpress?

[Chris Clawson]

Yes, that might be a better way to go! I have never tried to make queries 
directly from the Rest back end, but I had better start reading on it and 
see if I can understand what is written. With the Wordpress page making 
calls to a server side PHP script, it should be an easy matter to 
communicate with the localhost service running at port 4000. Of course, 
'easy' is a relative term. It would be very helpful if anyone wished to 
offer some demo snippets of how this might be started. Thanks for getting 
my mind to look in an obvious direction.

On Monday, January 17, 2022 at 3:48:57 PM UTC-5 deborah@lincoln.ac.nz 
wrote:

> Do you need to use direct queries to the database? Even if you are on the 
> same server it might be simpler to use the REST API (see documentation at 
> https://wiki.lyrasis.org/display/DSDOC7x/REST+API) and if you ever might 
> split the Wordpress site onto a different server it would be more robust.
>
>  
>
> Other options (probably not as good, but included for completeness) might 
> be to call an OAI feed (would work best by collection and/or by date - 
> https://wiki.lyrasis.org/display/DSDOC7x/OAI) or OpenSearch (can work via 
> keyword queries - 
> https://wiki.lyrasis.org/display/DSDOC7x/Business+Logic+Layer#BusinessLogicLayer-OpenSearchSupport
> ).
>
>  
>
> Deborah
>
>  
>
> *From:* dspac...@googlegroups.com  *On Behalf 
> Of *Chris Clawson
> *Sent:* Tuesday, 18 January 2022 6:28 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Using PHP for DSpace content in Wordpress?
>
>  
>
> *Caution:* This email originated from outside our organisation. Do not 
> click links or open attachments unless you recognize the sender and know 
> the content is safe.
>
>  
>
> I am trying to populate a Wordpress page with DSpace content, directly 
> from my own repository on the same server. I have a demo of this idea at 
> https://montaguearchive.org/index.php/hurricane-of-1938-page-3/ . This 
> example uses a php script to read a server side list of URIs I wish to 
> place in a gallery. It then uses CURL to make web calls to these links, 
> extract the information and then populate a web page in Wordpress.
>
> Might someone please help in achieving this by using direct queries to 
> DSpace's postgresql database?
>
> I am attaching a demo script based on the information at 
> https://wiki.lyrasis.org/display/DSPACE/The+metadatavalue+table . 
>
> When I edit this script to match my DSpace db login and use an 'id' (from 
> an exported metadata .csv), it will execute and echo the 
> dc.contributor.author of this item inside a terminal shell. Try this only 
> if you have installed the proper php module which allows a login to your 
> database. In my case, it was php7.1-pgsql.
>
> Is there better documentation somewhere which hints or explains how to use 
> the DSpace tables in a direct SQL query? Are there human readable forms in 
> the DSpace installation files, which would hint at some of these methods? 
>
> Might someone provide specific examples, based on this script I have 
> provided?
>
> Using an exported csv as a reference, I need to build queries for these 
> specific terms (using the 'id' of an item in the csv column 1):
>
> dc.description
>
> dc.identifier.uri
>
> dc.title
>
> ** and importantly, how may an image bitstream be retrieved in a 
> manner which can be placed in a web page?
>
> I really believe this technique may help promote DSpace by making it 
> easier to create visual galleries and presentations in Wordpress (or other) 
> websites. DSpace is an incredible resource for creating and managing 
> repositories, but really should have an easier way to present it's content 
> to an audience interested in casual browsing or authored presentations. My 
> web visitors are just not motivated when I tell them “go and explore the 
> database”. 
>
> Please help., 
>
> Chris
>
>  
>
>  
>
>  
>
> -- 
> 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/6dc88382-5ac6-480f-a1e2-2d0f3f849fdan%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/dspace-tech/6dc88382-5ac6-480f-a1e2-2d0f3f849fdan%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> --
>
> "The contents of this e-mai

[dspace-tech] Using PHP for DSpace content in Wordpress?

[Chris Clawson]

 

I am trying to populate a Wordpress page with DSpace content, directly from 
my own repository on the same server. I have a demo of this idea at 
https://montaguearchive.org/index.php/hurricane-of-1938-page-3/ . This 
example uses a php script to read a server side list of URIs I wish to 
place in a gallery. It then uses CURL to make web calls to these links, 
extract the information and then populate a web page in Wordpress.

Might someone please help in achieving this by using direct queries to 
DSpace's postgresql database?

I am attaching a demo script based on the information at 
https://wiki.lyrasis.org/display/DSPACE/The+metadatavalue+table . 

When I edit this script to match my DSpace db login and use an 'id' (from 
an exported metadata .csv), it will execute and echo the 
dc.contributor.author of this item inside a terminal shell. Try this only 
if you have installed the proper php module which allows a login to your 
database. In my case, it was php7.1-pgsql.

Is there better documentation somewhere which hints or explains how to use 
the DSpace tables in a direct SQL query? Are there human readable forms in 
the DSpace installation files, which would hint at some of these methods? 

Might someone provide specific examples, based on this script I have 
provided?

Using an exported csv as a reference, I need to build queries for these 
specific terms (using the 'id' of an item in the csv column 1):

dc.description

dc.identifier.uri

dc.title

** and importantly, how may an image bitstream be retrieved in a manner 
which can be placed in a web page?

I really believe this technique may help promote DSpace by making it easier 
to create visual galleries and presentations in Wordpress (or other) 
websites. DSpace is an incredible resource for creating and managing 
repositories, but really should have an easier way to present it's content 
to an audience interested in casual browsing or authored presentations. My 
web visitors are just not motivated when I tell them “go and explore the 
database”. 

Please help., 

Chris




-- 
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/6dc88382-5ac6-480f-a1e2-2d0f3f849fdan%40googlegroups.com.
<>

[dspace-tech] Re: DSpace 7 - Thumbnails in Browse Lists?

[Chris Clawson]

Has a solution to this been made? This feature is very important for my 
users. I really can't consider moving my live installation to DS 7 until 
this is available.

On Wednesday, September 22, 2021 at 3:19:10 PM UTC-4 Carl Jones wrote:

> Hi
>
> I was curious about the earlier in the summer, but since 7 has been 
> released has anyone customized their theme to add thumbnails to Browse 
> view?  Ideally, the ability to toggle between list and thumbnail (aka 
> gridElement) views as with Search results.  I know browse is implemented 
> differently and only use a simple list style format (according to Tim from 
> back in June). 
>
> I'm hoping this will eventually become a standard feature (esp. useful 
> with media-rich collections).
>
> Thanks,
>
> Carl
>
> ca...@mit.edu
> MIT Libraries
>

-- 
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/604f33e1-aed4-46f9-af02-a2b404d07808n%40googlegroups.com.

[dspace-tech] Re: Angular is up, but Cannot Login

[Chris Clawson]

Thanks, Tim.
My installation of DSpace 7 is mostly complete. It is up and running, I can 
login, add communities and items. Thanks to Mohamed AlMutairi, he has help 
investigate and resolve many points I hope get into the installation 
documentation. I have been trying to keep a diary on all this, and might 
consider submitting it to the team for review (when ready, if I knew where 
to submit it). At my skill level, there seems to be many missing points 
which might be provided for future users. It is a great package and I look 
forward to further development and a greater acceptance to a wider, less 
technical audience. This would especially benefit small libraries, non 
profit community collections and historical societies.

On Thursday, January 6, 2022 at 12:05:55 PM UTC-5 Tim Donohue wrote:

> Hi Chris,
>
> For hints on solving CORS errors, see the notes in our "Common 
> Installation Issues" in our documentation:
>
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-%22XMLHttpRequest..hasbeenblockedbyCORSpolicy%22or%22CORSerror%22or%22InvalidCORSrequest%22
>
> Usually, the cause is that the *backend* (REST API) local.cfg configs have 
> the wrong dspace.ui.url setting.
>
> Tim
>
> On Monday, December 27, 2021 at 6:52:16 PM UTC-6 Chris Clawson wrote:
>
>> Another Question: Below is the Rest portion of my environment.prods.ts 
>> file in /dspace-angular. I am using port 8443, rather than 443. Might this 
>> be causing all the 'CORS header ‘Access-Control-Allow-Origin’ missing). 
>> Status code: 403' messages?
>>
>>   rest: {
>>   ssl: true,
>>   host: 'mywebsite.com',
>>   port: 8443,
>>   // NOTE: Space is capitalized because 'namespace' is a reserved 
>> string in TypeScript
>>   nameSpace: '/server'
>>   }
>>
>> On Monday, December 27, 2021 at 7:36:51 PM UTC-5 Chris Clawson wrote:
>>
>>> More reading led me to my Firefox debug console. There are messages, 
>>> like "Cross-Origin Request Blocked: The Same Origin Policy disallows 
>>> reading the remote resource at https://myserver.com; all over the 
>>> place. I still have no idea what to do about it, but I guess this is where 
>>> I keep studying..
>>>
>>> On Monday, December 27, 2021 at 3:41:04 PM UTC-5 Chris Clawson wrote:
>>>
>>>> First DSpace 7 Angular UI screen! – (but) Unable to log in.
>>>>
>>>> I would appreciate some guidance. I was just successful in getting a 
>>>> DSpace 7 welcome screen from my remote webserver. I am unable to log in or 
>>>> browse the default database . Below the home page search box (Search the 
>>>> repository) is a message which says “error.top-level-communites “. If I 
>>>> click on any of the top menus (Communities, Statistics, etc) the screen 
>>>> attempts to load the page and then hangs (… loading..), as if waiting 
>>>> forever. I have added two Epersons and an Administrator using the ./dspace 
>>>> command line utility and am able to list them back, but the ui login says 
>>>> “invalid email or password”. So far, any command line database utility I 
>>>> have attempted has worked. The default database seems to be there 
>>>> (including my own two added epersons), but the ui doesn't appear to be 
>>>> accessing it. (right?)
>>>>
>>>> I had earlier issues installing Solr. Solr is running now as user 
>>>> 'solr'. The installation directories in /opt are owned by 'root', but the 
>>>> /server/solr/configsets are owned by 'solr'. When I try and run the 
>>>> command 
>>>> './dspace solr-reindex-statistics' I get an error: 
>>>>
>>>> Exception: Error from server at http://localhost:8983/solr: Path 
>>>> /dspace/solr/statistics must be relative to SOLR_HOME, SOLR_DATA_HOME 
>>>> coreRootDirectory. Set system property 'solr.allowPaths' to add other 
>>>> allowed paths.
>>>>
>>>> ?? Is this related to my primary problem? Where are these paths defined 
>>>> (SOLR_HOME, SOLR_DATA_HOME, etc)? I didn't see them in dspace.cfg or 
>>>> local.cfg.
>>>>
>>>> Some help in guiding the blind would be appreciated, here!
>>>>
>>>> Chris
>>>>
>>>>
>>>> Ubuntu 18.04
>>>>
>>>> KVM Cloud server
>>>>
>>>> 2 cpu cores 
>>>>
>>>> 4GB ram
>>>>
>>>

-- 
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/512bdd8b-5696-48d5-bdc2-343efe476d33n%40googlegroups.com.

[dspace-tech] PostgreSQL 14?

[Chris Clawson]

Is PostgreSQL 14 authorized for new installations of DSpace 7.1 or should 
we still be installing 13?

-- 
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/6b9aaf4e-4b74-40ca-9043-8a2292678ea5n%40googlegroups.com.

Re: [dspace-tech] Re: A How-To Solr installation on Ubuntu servers

[Chris Clawson]

 

Status and Tomcat configuration questions...


I have wiped my server of any previous installations of Solr and Tomcat (I 
think). I have been reviewing this thread and writing my out my procedure 
(to share later), but need to leave the work for New Years day now. Solr 
was installed first and then Tomcat 9 afterwards. 

Any effort I made to install Tomcat 9 using 'apt-get install tomcat9' did 
not install a binary build of apache-tomcat-9.0.56 (I don't know why). I 
have been following what seems to be a good manual procedure at 
https://www.makeuseof.com/a-step-by-step-guide-to-installing-apache-tomcat-linux/
 
. Both Solr and Tomcat9 now seem to be running well as services.

I am leaving the work day with the problem of configuring the server.xml 
and checking Tomcat instructions you have in the post “checking tomcat” 
(about 6 posts earlier).

   1. 
   
   I do not have any directory '/etc/tomcat'. I plan on editing the 
   server.xml from the /opt/tomcat/latest/conf directory and then copy that 
   directory's contents and paste it to a new /etc/tomcat directory (my 
   tomcat9 service is actually named 'tomcat.service'). Let me know if I am 
   wrong, but I think the 'Catalina' folder and other contents should be 
   copied there too. Is this a correct step to take?
   2. 
   
   I am looking at what you call the 'Catalina connector element' and am 
   not sure where that is. I see no mention of a localhost connector at 
127.0.0.1 
   port= 8080. Is this a totally new and added connector or a modification 
   of an existing one? Where would it be if I was looking at the default 
   server.xml from the distribution?
   3. 
   
   Doesn't this server.xml also have a edited SSL Connector for port 8443? 
   I presume the '


I am optimistic there is enough information and help here to get this all 
working well. Happy New Year to all and I hope the future remains tolerant 
of all these lay questions!


On Thursday, December 30, 2021 at 2:45:11 PM UTC-5 Chris Clawson wrote:

> Thanks - 
> I am in the process now of reviewing everything I have learned and you 
> have written out. I am attempting a re-install of Tomcat, Solr and will pay 
> close attention to all the Apache proxies and other configs you have 
> defined in this thread. PostgreSQL was a pain, but I think I have it right. 
> I will leave that and my other backend prerequisites  as they are now. So 
> my plan is to get the backend running again and then proceed following your 
> directions. If I screw up, I will just restore my backup image and start 
> over.
>
> montaguearchive.org is over a year old and I am a bad book keeper. The 
> port 8080 is to access the Wordpress html/php site and 8443 is to reach 
> Tomcat and DSpace 6.3. I think I realize this method is probably going to 
> change with DSpace 7. For now, I will just break the wordpress install of 
> meloware and focus on getting a functional DSpace server running with some 
> of the montaguearchive data. My partner is totally non technical (and even 
> older than I am), so he is going to need to be persuaded that upgrading his 
> project is a good idea. (So am I). I hope DSpace 7 has some great and 
> modern media handling features I can brag about. I also want to try out the 
> Jpeg2000 support. Cloud storage is expensive and some of my great Seadragon 
> image pyramids are over 2 GB in size! It would be great to shrink that.
> I will study this last post carefully, once I get to setting up Apache.
>
> On Thursday, December 30, 2021 at 2:26:40 PM UTC-5 Mohammad S. AlMutairi 
> wrote:
>
>> Chris:
>>
>> I never asked you why you are using port 8443 in your old server and the 
>> new one. Not sure why but in case you must use it and you must run DSpace 
>> on it the steps below is what you need to make it work Apache and DSpace 
>> work. One note you must pay attention two. You must use the file I sent you 
>> or at least use a reverse proxy in your apache configuration file to talk 
>> to tomecat and the frontend on port 8080 and 4000.
>>
>> First step you need to make sure apache are configured for that port in 
>> two files:
>> vi /etc/apache2/ports.conf
>> # 
>> ---
>> Listen 80
>>
>> 
>> Listen 443
>> Listen 8443
>> 
>>
>> 
>> Listen 443
>> Listen 8443
>> 
>> # 
>> ---
>>
>> Also you need to change meloware apache virtual host config file that I 
>> posted in the group list to run on that port:
>> vi /etc/apache2/sites-available/meloware.conf
>> 
>>
>> # Restart Apache
>> systemctl restart apache2
>&

Re: [dspace-tech] Re: A How-To Solr installation on Ubuntu servers

[Chris Clawson]

Thanks - 
I am in the process now of reviewing everything I have learned and you have 
written out. I am attempting a re-install of Tomcat, Solr and will pay 
close attention to all the Apache proxies and other configs you have 
defined in this thread. PostgreSQL was a pain, but I think I have it right. 
I will leave that and my other backend prerequisites  as they are now. So 
my plan is to get the backend running again and then proceed following your 
directions. If I screw up, I will just restore my backup image and start 
over.

montaguearchive.org is over a year old and I am a bad book keeper. The port 
8080 is to access the Wordpress html/php site and 8443 is to reach Tomcat 
and DSpace 6.3. I think I realize this method is probably going to change 
with DSpace 7. For now, I will just break the wordpress install of meloware 
and focus on getting a functional DSpace server running with some of the 
montaguearchive data. My partner is totally non technical (and even older 
than I am), so he is going to need to be persuaded that upgrading his 
project is a good idea. (So am I). I hope DSpace 7 has some great and 
modern media handling features I can brag about. I also want to try out the 
Jpeg2000 support. Cloud storage is expensive and some of my great Seadragon 
image pyramids are over 2 GB in size! It would be great to shrink that.
I will study this last post carefully, once I get to setting up Apache.

On Thursday, December 30, 2021 at 2:26:40 PM UTC-5 Mohammad S. AlMutairi 
wrote:

> Chris:
>
> I never asked you why you are using port 8443 in your old server and the 
> new one. Not sure why but in case you must use it and you must run DSpace 
> on it the steps below is what you need to make it work Apache and DSpace 
> work. One note you must pay attention two. You must use the file I sent you 
> or at least use a reverse proxy in your apache configuration file to talk 
> to tomecat and the frontend on port 8080 and 4000.
>
> First step you need to make sure apache are configured for that port in 
> two files:
> vi /etc/apache2/ports.conf
> # 
> ---
> Listen 80
>
> 
> Listen 443
> Listen 8443
> 
>
> 
> Listen 443
> Listen 8443
> 
> # 
> ---
>
> Also you need to change meloware apache virtual host config file that I 
> posted in the group list to run on that port:
> vi /etc/apache2/sites-available/meloware.conf
> 
>
> # Restart Apache
> systemctl restart apache2
>
> What you need then is to change local.cfg or dspace.cfg
> dspace.server.url = https://meloware.com:8443/server
> https:// meloware.com:8443
>
> # In environment.prod.ts change the port for the front rest server only. 
> Just leave the UI portion to localhost and port 4000
>   rest: {
> ssl: true,
> host: ' meloware.com ',
> port:  8443,
> nameSpace: '/server',
>
> # Check to see if everything is fine
> yarn config:check:rest
>
> # Build the frontend and restart it once everything is right.
> yarn run build:prod
>
>
> Hope it help.
>
>
> On Thu, Dec 30, 2021 at 5:26 PM Mohammad S. AlMutairi  
> wrote:
>
>> On Wednesday, December 29, 2021 at 4:03:40 PM UTC+3 Chris Clawson wrote:
>>
>>> Mohammad:
>>>
>>> The DSpace installation page didn't seem to provide any specific 
>>> procedure for installing Tomcat.
>>>
>> Hello Chris,
>> Not a specific step by step to follow for first timers but if you re-read 
>> the tomcat installation instructions and the other installations you will 
>> see almost everything an installer might need to know is pointed at or 
>> hinted. https://bit.ly/32DqZvw
>>  
>>
>>> I mostly followed the tutorial presented at 
>>> https://www.hostinger.com/tutorials/how-to-install-tomcat-on-ubuntu/ .
>>>
>> That's an outdated article. The author in the summary of that article 
>> says Tomcat6 is the only tomcat package available to install on Ubuntu 
>> 18.04. Nowadays Tomcat8 & Tomcat9 are available on Ubuntu 18.04 you can 
>> check them out if you update and upgrade your server as below. Using 
>> package managers (apt) to install packages will take care of future 
>> updates, bug fixes and security patches for.
>>
>> a) apt update -y
>> b) apt upgrade -y
>> c) apt-cache search tomcat | grep "^tomcat"
>>
>> I had installed Tomcat before I attempted an install of Solr. I do not 
>>> remember ever defining a user or password for the user/group tomcat. The 
>>> usermod, mkhomedir_helper, and passwd setup

Re: [dspace-tech] Re: A How-To Solr installation on Ubuntu servers

[Chris Clawson]

 

This current effort is just practice for bigger things. Perhaps I should 
backup this work and then begin again with a fresh install. Many questions 
have been answered here and a second try should go much faster. My 
installation still has differences with the documentation, which may be 
fixable, but could still complicate any support I might hope to get later 
on. 

A second try will also give me the opportunity to create and verify a 
checklist procedure for future installations. This might be useful to 
others later on.

Mohammad, you have been a great amount of help. I also offer my respects 
and appreciation to everyone involved with DSpace development. This is a 
valuable project and I hope my experience with it will make a small 
contribution to it's acceptance to the wider global community.


Chris Clawson


On Wednesday, December 29, 2021 at 8:03:40 AM UTC-5 Chris Clawson wrote:

> Please allow a bit of 'off topic' comment, so you and the DSpace 
> documentation folks may appreciate what I am doing. I had been out of 
> school more than ten years before the first 8 bit PCs became available in 
> the home. I have no direct contact with any I.T. Professionals and needed 
> to learn everything I know off of the internet. All of my cyberspace 
> learning has been self directed and focused specifically on reaching my 
> project goals, rather than getting a broad education on any topic. DSpace 
> is a valuable tool I am trying to promote for community historical 
> societies and small museums.
>
> I am fairly familiar with a LAMP server. I understand how to install and 
> configure a website. My live site is running both Wordpress (with LAMP) and 
> DSpace 6.3 (Tomcat). This Tomcat has been my first exposure with the idea 
> of a java server (or java anything).
>
> Respectfully, these installation instructions for DSpace are the best I 
> have available, but often leave me guessing about details in procedure or 
> direct me elsewhere for further instruction. I am often confused at those 
> sites or find that the topic has nothing to do with installing a module in 
> a remote web server. Mohammad is asking me now about how and why I did 
> things in a certain way. The general answer is that I was unable to see a 
> clear procedure defined in the DSpace installation page and needed to read 
> and try stuff elsewhere, in order to be able to continue my project. This 
> help you all are offering is leading me through a 'dry run' before I 
> attempt to upgrade my live server at montaguearchive.org . If I can learn 
> this properly, I might consider working on a tutorial video and 
> documentation on installing DSpace (with the blessing and guidance of the 
> folks at Lyrasis). If I can understand this, at my level of skill, I may be 
> able to present it in a way that could be appreciated by a much wider 
> audience of folks.
>
> ***
>
> Mohammad:
>
> The DSpace installation page didn't seem to provide any specific procedure 
> for installing Tomcat. I mostly followed the tutorial presented at 
> https://www.hostinger.com/tutorials/how-to-install-tomcat-on-ubuntu/ . I 
> had installed Tomcat before I attempted an install of Solr. I do not 
> remember ever defining a user or password for the user/group tomcat. The 
> usermod, mkhomedir_helper, and passwd setup was critical in getting the 
> install_solr_service.sh script to run! I would never have figured this out 
> on my own and I thank you again!
>
> I re-ran the following commands:
>
> curl http://localhost:8983/solr/admin/cores
> curl http://localhost:8983/solr/admin/cores?action=STATUS 
>
>
> There were a number of permission errors. Here was the condition of a 
> directory before I chown'd everything to tomcat:tomcat :
>
> root@media:/var/solr/data#
>
> drwxr-xr-x 3 root root 4096 Dec 28 17:25 authority
>
> drwxrwxr-x 2 tomcat tomcat 4096 Dec 28 17:25 filestore
>
> drwxr-xr-x 3 root root 4096 Dec 28 17:25 oai
>
> drwxr-xr-x 3 root root 4096 Dec 28 17:25 search
>
> -rw-r- 1 tomcat tomcat 2427 Dec 28 17:22 solr.xml
>
> drwxr-xr-x 3 root root 4096 Dec 28 17:25 statistics
>
> drwxrwxr-x 2 tomcat tomcat 4096 Dec 28 17:25 userfiles
>
> -rw-r- 1 tomcat tomcat 1048 Dec 28 17:22 zoo.cfg
>
> root@media:/var/solr/data#
>
>
> The curl status commands are reporting a lot of detail about Solr and more 
> than I should paste into this post.
>
> PM2 is installed, but I need to start it manually. How can I make it run 
> when the system boots?
>
> I just got up and see that you have sent me a lot of information, related 
> to the status you think my install is at this morning. Thanks and give me 
> time to study it all!
>
> C.
>
>
>
>
> On Wednesday, December 29, 2021 at 7:31:14 AM UTC

Re: [dspace-tech] Re: A How-To Solr installation on Ubuntu servers

[Chris Clawson]

e 
>  
> ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
>  SSLHonorCipherOrder off
>  SSLSessionTickets   off
>  RequestHeader set X-Forwarded-Proto "https" env=HTTPS
>
>
>   AddDefaultCharset Off
>   Order allow,deny
>   Allow from all
>
>
>  ProxyPass /server http://localhost:8080/server
>  ProxyPassReverse /server http://localhost:8080/server
>  #ProxyPass /solr http://localhost:8983/
>  #ProxyPassReverse /solr http://localhost:8983/
>  ProxyPass / http://localhost:4000/
>  ProxyPassReverse / http://localhost:4000/
> 
>
> ------
>
> # Enable the dspace site you just created in the step above.
> a2ensite dspace.conf
>
> systemctl restart apache2
> #  End of Apache virtual host & Reverse 
> proxy Configuration ###
>
> Finally, I hope I was able to help you or at least was able to clear where 
> you might have gone wrong during the configuration. If there is anyone to 
> thank it should go to the beautiful minds behind DSpace. Who consumed their 
> time and energy to make it what it is today. Thank you and you have our 
> respects.
>
> On Wed, Dec 29, 2021 at 3:19 AM Chris Clawson  
> wrote:
>
>> A bit late?? I will have this answered tomorrow (12/28). Solr now 
>> installed completely and I have fixed other errors. My web browser shows 
>> loads of CORS errors but less than I had.
>> I will make a summary and answer the tomcat install question later.
>> My Rest runs out of tomcat. You can view quite a summary by looking at my 
>> HAL browser at: https://meloware.com:8443/#/api  SSL port 8443 is where 
>> my DSpace 6.3 install runs at https://montaguearchive.org:8443/ . Maybe 
>> I have a problem using this port. Thanks and good night.
>>
>> On Tuesday, December 28, 2021 at 7:03:59 PM UTC-5 Mohammad S. AlMutairi 
>> wrote:
>>
>>> It is a little bit late here. Looking at what you posted as a tomcat 
>>> entry in the /etc/passwd file showed the tomcat user was either created 
>>> manually or by the solr installation script but was not created by apt ( 
>>> apt install tomcat9 ) so here comes a couple of questions. How did you 
>>> install tomcat? and which service did you install first tomcat? or solr?. 
>>> See how the entry looks like if it was installed by apt. 
>>> ( tomcat:x:999:999:Apache Tomcat:/:/sbin/nologin ). What I mean Apache 
>>> Tomcat is what's in the name field.
>>>
>>>
>>>
>>> On Wednesday, December 29, 2021 at 2:01:10 AM UTC+3 Chris Clawson wrote:
>>>
>>>> Oops! I just saw this question after making the changes to the tomcat 
>>>> user. The command now produces:
>>>> $ grep tomcat /etc/passwd
>>>> tomcat:x:1003:1004::/home/tomcat:/bin/bash
>>>>
>>>> On Tuesday, December 28, 2021 at 5:42:30 PM UTC-5 Mohammad S. AlMutairi 
>>>> wrote:
>>>>
>>>>> I was able to replicate the issue you have (see the attached 
>>>>> snapshot). It turned out it's happening when the user tomcat is defaulted 
>>>>> to have the login shell in /etc/passwd set to /sbin/nologin .. To resolve 
>>>>> it you need to execute the commands you see below in the sequence you see 
>>>>> them and then start the solr installation in the first post.
>>>>>
>>>>> 1) usermod -d /home/tomcat -s /bin/bash tomcat
>>>>> 2) mkhomedir_helper tomcat
>>>>> 3) passwd tomcat
>>>>>
>>>>> Good luck
>>>>> On Tuesday, December 28, 2021 at 9:37:23 PM UTC+3 Chris Clawson wrote:
>>>>>
>>>>>> This is a KVM cloud server hosted at http://www.tektonic.net/. It is 
>>>>>> a basic LAMP installation and has a Wordpress site installed (
>>>>>> meloware.com) . I am trying to install DSpace 7 in preparation for 
>>>>>> upgrading a live database DSpace 6.3 installation on a different cloud 
>>>>>> VPS. 
>>>>>> This Ubuntu 18 vps is a service I have been using for a few years. It is 
>>>>>> not a new installation. The vps is installed in a very minimal 
>>>>>> conf

[dspace-tech] Re: A How-To Solr installation on Ubuntu servers

[Chris Clawson]

A bit late?? I will have this answered tomorrow (12/28). Solr now installed 
completely and I have fixed other errors. My web browser shows loads of 
CORS errors but less than I had.
I will make a summary and answer the tomcat install question later.
My Rest runs out of tomcat. You can view quite a summary by looking at my 
HAL browser at: https://meloware.com:8443/#/api  SSL port 8443 is where my 
DSpace 6.3 install runs at https://montaguearchive.org:8443/ . Maybe I have 
a problem using this port. Thanks and good night.

On Tuesday, December 28, 2021 at 7:03:59 PM UTC-5 Mohammad S. AlMutairi 
wrote:

> It is a little bit late here. Looking at what you posted as a tomcat entry 
> in the /etc/passwd file showed the tomcat user was either created manually 
> or by the solr installation script but was not created by apt ( apt install 
> tomcat9 ) so here comes a couple of questions. How did you install tomcat? 
> and which service did you install first tomcat? or solr?. See how the entry 
> looks like if it was installed by apt. ( tomcat:x:999:999:Apache 
> Tomcat:/:/sbin/nologin ). What I mean Apache Tomcat is what's in the name 
> field.
>
>
>
> On Wednesday, December 29, 2021 at 2:01:10 AM UTC+3 Chris Clawson wrote:
>
>> Oops! I just saw this question after making the changes to the tomcat 
>> user. The command now produces:
>> $ grep tomcat /etc/passwd
>> tomcat:x:1003:1004::/home/tomcat:/bin/bash
>>
>> On Tuesday, December 28, 2021 at 5:42:30 PM UTC-5 Mohammad S. AlMutairi 
>> wrote:
>>
>>> I was able to replicate the issue you have (see the attached snapshot). 
>>> It turned out it's happening when the user tomcat is defaulted to have the 
>>> login shell in /etc/passwd set to /sbin/nologin .. To resolve it you need 
>>> to execute the commands you see below in the sequence you see them and then 
>>> start the solr installation in the first post.
>>>
>>> 1) usermod -d /home/tomcat -s /bin/bash tomcat
>>> 2) mkhomedir_helper tomcat
>>> 3) passwd tomcat
>>>
>>> Good luck
>>> On Tuesday, December 28, 2021 at 9:37:23 PM UTC+3 Chris Clawson wrote:
>>>
>>>> This is a KVM cloud server hosted at http://www.tektonic.net/. It is a 
>>>> basic LAMP installation and has a Wordpress site installed (
>>>> meloware.com) . I am trying to install DSpace 7 in preparation for 
>>>> upgrading a live database DSpace 6.3 installation on a different cloud 
>>>> VPS. 
>>>> This Ubuntu 18 vps is a service I have been using for a few years. It is 
>>>> not a new installation. The vps is installed in a very minimal 
>>>> configuration and is not likely to have any packages installed that I 
>>>> didn't do myself. The service allows 2 cpu cores and 4GB of ram. I have 
>>>> full root access and can only re-install everything if I break it. I 
>>>> believe Ubuntu 18 is compatible and I think I have  installed all the 
>>>> packages required for DSpace 7. When building this DSpace with yarn, my 
>>>> system ran out of memory. I was eventually able to get it to complete by 
>>>> shutting down Tomcat during the build process.
>>>>
>>>> The command 'sestatus' was not available as a command, so I installed 
>>>> policycoreutils. Now the command says "SELinux status: 
>>>> disabled".
>>>>
>>>> The command, aa-status, produced the following:
>>>> root@media:/# aa-status
>>>> apparmor module is loaded.
>>>> 10 profiles are loaded.
>>>> 10 profiles are in enforce mode.
>>>>/sbin/dhclient
>>>>/usr/bin/man
>>>>/usr/lib/NetworkManager/nm-dhcp-client.action
>>>>/usr/lib/NetworkManager/nm-dhcp-helper
>>>>/usr/lib/connman/scripts/dhclient-script
>>>>/usr/sbin/mysqld
>>>>/usr/sbin/ntpd
>>>>/usr/sbin/tcpdump
>>>>man_filter
>>>>man_groff
>>>> 0 profiles are in complain mode.
>>>> 1 processes have profiles defined.
>>>> 1 processes are in enforce mode.
>>>>/usr/sbin/mysqld (867)
>>>> 0 processes are in complain mode.
>>>> 0 processes are unconfined but have a profile defined.
>>>> root@media:/#
>>>>
>>>> It looks like someone is hammering ports for my root access. This  IP  
>>>> 221.131.165.50 is not anything I am part of and is probably a hacker. Here 
>>>> are the last few lines from the journal:
>>>>
>>>> Dec 28 12:15:11 

[dspace-tech] Re: A How-To Solr installation on Ubuntu servers

[Chris Clawson]

Oops! I just saw this question after making the changes to the tomcat user. 
The command now produces:
$ grep tomcat /etc/passwd
tomcat:x:1003:1004::/home/tomcat:/bin/bash

On Tuesday, December 28, 2021 at 5:42:30 PM UTC-5 Mohammad S. AlMutairi 
wrote:

> I was able to replicate the issue you have (see the attached snapshot). It 
> turned out it's happening when the user tomcat is defaulted to have the 
> login shell in /etc/passwd set to /sbin/nologin .. To resolve it you need 
> to execute the commands you see below in the sequence you see them and then 
> start the solr installation in the first post.
>
> 1) usermod -d /home/tomcat -s /bin/bash tomcat
> 2) mkhomedir_helper tomcat
> 3) passwd tomcat
>
> Good luck
> On Tuesday, December 28, 2021 at 9:37:23 PM UTC+3 Chris Clawson wrote:
>
>> This is a KVM cloud server hosted at http://www.tektonic.net/. It is a 
>> basic LAMP installation and has a Wordpress site installed (meloware.com) 
>> . I am trying to install DSpace 7 in preparation for upgrading a live 
>> database DSpace 6.3 installation on a different cloud VPS. This Ubuntu 18 
>> vps is a service I have been using for a few years. It is not a new 
>> installation. The vps is installed in a very minimal configuration and is 
>> not likely to have any packages installed that I didn't do myself. The 
>> service allows 2 cpu cores and 4GB of ram. I have full root access and can 
>> only re-install everything if I break it. I believe Ubuntu 18 is compatible 
>> and I think I have  installed all the packages required for DSpace 7. When 
>> building this DSpace with yarn, my system ran out of memory. I was 
>> eventually able to get it to complete by shutting down Tomcat during the 
>> build process.
>>
>> The command 'sestatus' was not available as a command, so I installed 
>> policycoreutils. Now the command says "SELinux status: 
>> disabled".
>>
>> The command, aa-status, produced the following:
>> root@media:/# aa-status
>> apparmor module is loaded.
>> 10 profiles are loaded.
>> 10 profiles are in enforce mode.
>>/sbin/dhclient
>>/usr/bin/man
>>/usr/lib/NetworkManager/nm-dhcp-client.action
>>/usr/lib/NetworkManager/nm-dhcp-helper
>>/usr/lib/connman/scripts/dhclient-script
>>/usr/sbin/mysqld
>>/usr/sbin/ntpd
>>/usr/sbin/tcpdump
>>man_filter
>>man_groff
>> 0 profiles are in complain mode.
>> 1 processes have profiles defined.
>> 1 processes are in enforce mode.
>>/usr/sbin/mysqld (867)
>> 0 processes are in complain mode.
>> 0 processes are unconfined but have a profile defined.
>> root@media:/#
>>
>> It looks like someone is hammering ports for my root access. This  IP  
>> 221.131.165.50 is not anything I am part of and is probably a hacker. Here 
>> are the last few lines from the journal:
>>
>> Dec 28 12:15:11 media sshd[2824]: Disconnected from authenticating user 
>> root 221.131.165.50 port 19567 [preauth]
>> Dec 28 12:15:11 media sshd[2824]: PAM 2 more authentication failures; 
>> logname= uid=0 euid=0 tty=ssh ruser= rhost=221.131.165.50  user=root
>> Dec 28 12:15:13 media sshd[2826]: pam_unix(sshd:auth): authentication 
>> failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.131.165.50 
>>  user=root
>> Dec 28 12:15:15 media sshd[2826]: Failed password for root from 
>> 221.131.165.50 port 16020 ssh2
>> Dec 28 12:15:17 media sshd[2826]: Failed password for root from 
>> 221.131.165.50 port 16020 ssh2
>>
>> *
>> Isn't the problem now related to permissions and setting up solr as a 
>> startup service? I can always change any user:group ownership as needed. 
>> When I used the DSpace 7 installation page, Solr would only install without 
>> making any changes to the owners or permissions. Solr only installed when 
>> the default 'solr' user was created. Any attempt to mention 'tomcat' 
>> resulted in the same error I am seeing now, when it seems the solr.service 
>> is being setup.
>>
>> I appreciate this help! DSpace is far more valuable than simply confining 
>> it to universities. There are many civil organizations in the world, which 
>> have major private collections and need to share them. Besides, many of we 
>> historians are dying off from old age. If we can't organize these 
>> collections and contribute our historic metadata, what happens to the 
>> history after we are all gone?
>> On Tuesday, December 28, 2021 at 12:53:32 PM UTC-5 Mohammad S. AlMutairi 
>> wrote:
>>
>>> Honestly I'm guessing here because the lack 

[dspace-tech] Re: A How-To Solr installation on Ubuntu servers

[Chris Clawson]

I will try that. I need to give it a rest and regroup my thinking. After I 
have summarized what I have done, I can ask more intelligent questions, if 
needed. I am guessing it is late for you, so thanks and we may talk later.
C.

On Tuesday, December 28, 2021 at 5:42:30 PM UTC-5 Mohammad S. AlMutairi 
wrote:

> I was able to replicate the issue you have (see the attached snapshot). It 
> turned out it's happening when the user tomcat is defaulted to have the 
> login shell in /etc/passwd set to /sbin/nologin .. To resolve it you need 
> to execute the commands you see below in the sequence you see them and then 
> start the solr installation in the first post.
>
> 1) usermod -d /home/tomcat -s /bin/bash tomcat
> 2) mkhomedir_helper tomcat
> 3) passwd tomcat
>
> Good luck
> On Tuesday, December 28, 2021 at 9:37:23 PM UTC+3 Chris Clawson wrote:
>
>> This is a KVM cloud server hosted at http://www.tektonic.net/. It is a 
>> basic LAMP installation and has a Wordpress site installed (meloware.com) 
>> . I am trying to install DSpace 7 in preparation for upgrading a live 
>> database DSpace 6.3 installation on a different cloud VPS. This Ubuntu 18 
>> vps is a service I have been using for a few years. It is not a new 
>> installation. The vps is installed in a very minimal configuration and is 
>> not likely to have any packages installed that I didn't do myself. The 
>> service allows 2 cpu cores and 4GB of ram. I have full root access and can 
>> only re-install everything if I break it. I believe Ubuntu 18 is compatible 
>> and I think I have  installed all the packages required for DSpace 7. When 
>> building this DSpace with yarn, my system ran out of memory. I was 
>> eventually able to get it to complete by shutting down Tomcat during the 
>> build process.
>>
>> The command 'sestatus' was not available as a command, so I installed 
>> policycoreutils. Now the command says "SELinux status: 
>> disabled".
>>
>> The command, aa-status, produced the following:
>> root@media:/# aa-status
>> apparmor module is loaded.
>> 10 profiles are loaded.
>> 10 profiles are in enforce mode.
>>/sbin/dhclient
>>/usr/bin/man
>>/usr/lib/NetworkManager/nm-dhcp-client.action
>>/usr/lib/NetworkManager/nm-dhcp-helper
>>/usr/lib/connman/scripts/dhclient-script
>>/usr/sbin/mysqld
>>/usr/sbin/ntpd
>>/usr/sbin/tcpdump
>>man_filter
>>man_groff
>> 0 profiles are in complain mode.
>> 1 processes have profiles defined.
>> 1 processes are in enforce mode.
>>/usr/sbin/mysqld (867)
>> 0 processes are in complain mode.
>> 0 processes are unconfined but have a profile defined.
>> root@media:/#
>>
>> It looks like someone is hammering ports for my root access. This  IP  
>> 221.131.165.50 is not anything I am part of and is probably a hacker. Here 
>> are the last few lines from the journal:
>>
>> Dec 28 12:15:11 media sshd[2824]: Disconnected from authenticating user 
>> root 221.131.165.50 port 19567 [preauth]
>> Dec 28 12:15:11 media sshd[2824]: PAM 2 more authentication failures; 
>> logname= uid=0 euid=0 tty=ssh ruser= rhost=221.131.165.50  user=root
>> Dec 28 12:15:13 media sshd[2826]: pam_unix(sshd:auth): authentication 
>> failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.131.165.50 
>>  user=root
>> Dec 28 12:15:15 media sshd[2826]: Failed password for root from 
>> 221.131.165.50 port 16020 ssh2
>> Dec 28 12:15:17 media sshd[2826]: Failed password for root from 
>> 221.131.165.50 port 16020 ssh2
>>
>> *
>> Isn't the problem now related to permissions and setting up solr as a 
>> startup service? I can always change any user:group ownership as needed. 
>> When I used the DSpace 7 installation page, Solr would only install without 
>> making any changes to the owners or permissions. Solr only installed when 
>> the default 'solr' user was created. Any attempt to mention 'tomcat' 
>> resulted in the same error I am seeing now, when it seems the solr.service 
>> is being setup.
>>
>> I appreciate this help! DSpace is far more valuable than simply confining 
>> it to universities. There are many civil organizations in the world, which 
>> have major private collections and need to share them. Besides, many of we 
>> historians are dying off from old age. If we can't organize these 
>> collections and contribute our historic metadata, what happens to the 
>> history after we are all gone?
>> On Tuesday, December 28, 2021 at 12:53:32 PM UTC-5 Mohammad S. AlMutairi 
>> wrote:
&g

[dspace-tech] Re: A How-To Solr installation on Ubuntu servers

[Chris Clawson]

This is a KVM cloud server hosted at http://www.tektonic.net/. It is a 
basic LAMP installation and has a Wordpress site installed (meloware.com) . 
I am trying to install DSpace 7 in preparation for upgrading a live 
database DSpace 6.3 installation on a different cloud VPS. This Ubuntu 18 
vps is a service I have been using for a few years. It is not a new 
installation. The vps is installed in a very minimal configuration and is 
not likely to have any packages installed that I didn't do myself. The 
service allows 2 cpu cores and 4GB of ram. I have full root access and can 
only re-install everything if I break it. I believe Ubuntu 18 is compatible 
and I think I have  installed all the packages required for DSpace 7. When 
building this DSpace with yarn, my system ran out of memory. I was 
eventually able to get it to complete by shutting down Tomcat during the 
build process.

The command 'sestatus' was not available as a command, so I installed 
policycoreutils. Now the command says "SELinux status: 
disabled".

The command, aa-status, produced the following:
root@media:/# aa-status
apparmor module is loaded.
10 profiles are loaded.
10 profiles are in enforce mode.
   /sbin/dhclient
   /usr/bin/man
   /usr/lib/NetworkManager/nm-dhcp-client.action
   /usr/lib/NetworkManager/nm-dhcp-helper
   /usr/lib/connman/scripts/dhclient-script
   /usr/sbin/mysqld
   /usr/sbin/ntpd
   /usr/sbin/tcpdump
   man_filter
   man_groff
0 profiles are in complain mode.
1 processes have profiles defined.
1 processes are in enforce mode.
   /usr/sbin/mysqld (867)
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
root@media:/#

It looks like someone is hammering ports for my root access. This  IP  
221.131.165.50 is not anything I am part of and is probably a hacker. Here 
are the last few lines from the journal:

Dec 28 12:15:11 media sshd[2824]: Disconnected from authenticating user 
root 221.131.165.50 port 19567 [preauth]
Dec 28 12:15:11 media sshd[2824]: PAM 2 more authentication failures; 
logname= uid=0 euid=0 tty=ssh ruser= rhost=221.131.165.50  user=root
Dec 28 12:15:13 media sshd[2826]: pam_unix(sshd:auth): authentication 
failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.131.165.50 
 user=root
Dec 28 12:15:15 media sshd[2826]: Failed password for root from 
221.131.165.50 port 16020 ssh2
Dec 28 12:15:17 media sshd[2826]: Failed password for root from 
221.131.165.50 port 16020 ssh2

*
Isn't the problem now related to permissions and setting up solr as a 
startup service? I can always change any user:group ownership as needed. 
When I used the DSpace 7 installation page, Solr would only install without 
making any changes to the owners or permissions. Solr only installed when 
the default 'solr' user was created. Any attempt to mention 'tomcat' 
resulted in the same error I am seeing now, when it seems the solr.service 
is being setup.

I appreciate this help! DSpace is far more valuable than simply confining 
it to universities. There are many civil organizations in the world, which 
have major private collections and need to share them. Besides, many of we 
historians are dying off from old age. If we can't organize these 
collections and contribute our historic metadata, what happens to the 
history after we are all gone?
On Tuesday, December 28, 2021 at 12:53:32 PM UTC-5 Mohammad S. AlMutairi 
wrote:

> Honestly I'm guessing here because the lack of information about your 
> server and or what has been done to it :-). As a first guess do you have 
> SELinux or AppArmor installed and enabled on your server? Can you check 
> it by typing as root the commands you see below.
>
> # To check SELinux
> sestatus
>
> # To check AppArmor
> aa-status
>
> # I want you to send the result of this command too.
> journalctl -xe
>
> I'll walk you through it if you provide enough information to pin point 
> the issue with your server and it's setup.  You should've installed Ubuntu 
> 20.04 LTS instead of 18.04 LTS . See why you should've done that here 
> https://wiki.ubuntu.com/Releases
> On Tuesday, December 28, 2021 at 8:05:09 PM UTC+3 Chris Clawson wrote:
>
>> I believe this has happened before... Problems begin with step 'f'. The 
>> following is the output from the bash command:
>>
>> root@media:/build# bash ./install_solr_service.sh solr-8.11.1.tgz -f
>> Extracting solr-8.11.1.tgz to /opt
>> Installing symlink /opt/solr -> /opt/solr-8.11.1 ...
>> Installing /etc/init.d/solr script ...
>> Installing /etc/default/solr.in.sh ...
>> Service solr installed.
>> Customize Solr startup configuration in /etc/default/solr.in.sh
>> Job for solr.service failed because the control process exited with error 
>> code.
>> See "systemctl status solr.service" and "journalctl -xe" for details.
>> ● so

[dspace-tech] Re: A How-To Solr installation on Ubuntu servers

[Chris Clawson]

I guess things go 'wrong' when trying to setup solr as a service to run at 
system boot time. The script, 'solr.in.sh' gets written into the 
/etc/default  directory. It get the user/group settings of root:tomcat . 
Yes, I am logged in via SSH as root. I believe the /var/solr directories 
are owned by tomcat:tomcat and the /var/solr/logs directory is empty. The 
installation directory at /opt/solr-8.11.1 and the sym link 'solr' are 
root:root as well as all the recursive contents. Is this right? 
On Tuesday, December 28, 2021 at 12:05:09 PM UTC-5 Chris Clawson wrote:

> I believe this has happened before... Problems begin with step 'f'. The 
> following is the output from the bash command:
>
> root@media:/build# bash ./install_solr_service.sh solr-8.11.1.tgz -f
> Extracting solr-8.11.1.tgz to /opt
> Installing symlink /opt/solr -> /opt/solr-8.11.1 ...
> Installing /etc/init.d/solr script ...
> Installing /etc/default/solr.in.sh ...
> Service solr installed.
> Customize Solr startup configuration in /etc/default/solr.in.sh
> Job for solr.service failed because the control process exited with error 
> code.
> See "systemctl status solr.service" and "journalctl -xe" for details.
> ● solr.service - LSB: Controls Apache Solr as a Service
>Loaded: loaded (/etc/init.d/solr; generated)
>Active: failed (Result: exit-code) since Tue 2021-12-28 11:00:48 CST; 
> 5s ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 1474 ExecStart=/etc/init.d/solr start (code=exited, 
> status=1/FAILURE)
>
> Dec 28 11:00:48 media systemd[1]: Starting LSB: Controls Apache Solr as a 
> Service...
> Dec 28 11:00:48 media su[1476]: Successful su for tomcat by root
> Dec 28 11:00:48 media su[1476]: + ??? root:tomcat
> Dec 28 11:00:48 media su[1476]: pam_unix(su:session): session opened for 
> user tomcat by (uid=0)
> Dec 28 11:00:48 media su[1476]: pam_unix(su:session): session closed for 
> user tomcat
> Dec 28 11:00:48 media systemd[1]: solr.service: Control process exited, 
> code=exited status=1
> Dec 28 11:00:48 media systemd[1]: solr.service: Failed with result 
> 'exit-code'.
> Dec 28 11:00:48 media systemd[1]: Failed to start LSB: Controls Apache 
> Solr as a Service.
> root@media:/build#
>
> On Tuesday, December 28, 2021 at 9:21:25 AM UTC-5 Mohammad S. AlMutairi 
> wrote:
>
>> Hello Chris,
>>
>> Your solr installation is broken so you really really really must remove 
>> the old installation and begin a fresh install. All the provided 
>> instructions is very simple and easy to follow so just follow it. Regarding 
>> step (e) it just another and easier way of changing SOLR_USER=solr to 
>> SOLR_USER=tomcat using perl substitution. Don't stop at it or the (g) step 
>> just remove the old solr and install solr following the installation steps 
>> above but you MUST BE ROOT during the removal or the installing of Solr to 
>> overcome any permission issues you might confront.
>>
>>  Here is what you suppose to see if Solr and dspace cores are done 
>> correctly. This is part of it.#
>> "search":{
>>   "name":"search",
>>   "instanceDir":"/var/solr/data/search",
>>   "dataDir":"/var/solr/data/search/data/",
>>   "config":"solrconfig.xml",
>>   "schema":"schema.xml",
>>   "startTime":"2021-12-28T10:55:06.841Z",
>>   "uptime":11865277,
>>   "index":{
>> "numDocs":45760,
>> "maxDoc":45760,
>> "deletedDocs":0,
>> "indexHeapUsageBytes":489928,
>> "version":678,
>> "segmentCount":22,
>> "current":true,
>> "hasDeletions":false,
>> 
>> "directory":"org.apache.lucene.store.NRTCachingDirectory:NRTCachingDirectory(MMapDirectory@/var/solr/data/search/data/index
>>  
>> lockFactory=org.apache.lucene.store.NativeFSLockFactory@12cd8c11; 
>> maxCacheMB=48.0 maxMergeSizeMB=4.0)",
>> "segmentsFile":"segments_2z",
>> "segmentsFileSizeInBytes":1947,
>> "userData":{
>>   "commitCommandVer":"0",
>>   "commitTimeMSec":"1640647856055"},
>> "lastModified":"2021-12-27T23:30:56.055Z",
>> "sizeInBytes":1641346285,
>> "size":"1.53 GB"}},
>> "statistics":{
>>   "name"

[dspace-tech] Re: A How-To Solr installation on Ubuntu servers

[Chris Clawson]

I believe this has happened before... Problems begin with step 'f'. The 
following is the output from the bash command:

root@media:/build# bash ./install_solr_service.sh solr-8.11.1.tgz -f
Extracting solr-8.11.1.tgz to /opt
Installing symlink /opt/solr -> /opt/solr-8.11.1 ...
Installing /etc/init.d/solr script ...
Installing /etc/default/solr.in.sh ...
Service solr installed.
Customize Solr startup configuration in /etc/default/solr.in.sh
Job for solr.service failed because the control process exited with error 
code.
See "systemctl status solr.service" and "journalctl -xe" for details.
● solr.service - LSB: Controls Apache Solr as a Service
   Loaded: loaded (/etc/init.d/solr; generated)
   Active: failed (Result: exit-code) since Tue 2021-12-28 11:00:48 CST; 5s 
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 1474 ExecStart=/etc/init.d/solr start (code=exited, 
status=1/FAILURE)

Dec 28 11:00:48 media systemd[1]: Starting LSB: Controls Apache Solr as a 
Service...
Dec 28 11:00:48 media su[1476]: Successful su for tomcat by root
Dec 28 11:00:48 media su[1476]: + ??? root:tomcat
Dec 28 11:00:48 media su[1476]: pam_unix(su:session): session opened for 
user tomcat by (uid=0)
Dec 28 11:00:48 media su[1476]: pam_unix(su:session): session closed for 
user tomcat
Dec 28 11:00:48 media systemd[1]: solr.service: Control process exited, 
code=exited status=1
Dec 28 11:00:48 media systemd[1]: solr.service: Failed with result 
'exit-code'.
Dec 28 11:00:48 media systemd[1]: Failed to start LSB: Controls Apache Solr 
as a Service.
root@media:/build#

On Tuesday, December 28, 2021 at 9:21:25 AM UTC-5 Mohammad S. AlMutairi 
wrote:

> Hello Chris,
>
> Your solr installation is broken so you really really really must remove 
> the old installation and begin a fresh install. All the provided 
> instructions is very simple and easy to follow so just follow it. Regarding 
> step (e) it just another and easier way of changing SOLR_USER=solr to 
> SOLR_USER=tomcat using perl substitution. Don't stop at it or the (g) step 
> just remove the old solr and install solr following the installation steps 
> above but you MUST BE ROOT during the removal or the installing of Solr to 
> overcome any permission issues you might confront.
>
>  Here is what you suppose to see if Solr and dspace cores are done 
> correctly. This is part of it.#
> "search":{
>   "name":"search",
>   "instanceDir":"/var/solr/data/search",
>   "dataDir":"/var/solr/data/search/data/",
>   "config":"solrconfig.xml",
>   "schema":"schema.xml",
>   "startTime":"2021-12-28T10:55:06.841Z",
>   "uptime":11865277,
>   "index":{
> "numDocs":45760,
> "maxDoc":45760,
> "deletedDocs":0,
> "indexHeapUsageBytes":489928,
> "version":678,
> "segmentCount":22,
> "current":true,
> "hasDeletions":false,
> 
> "directory":"org.apache.lucene.store.NRTCachingDirectory:NRTCachingDirectory(MMapDirectory@/var/solr/data/search/data/index
>  
> lockFactory=org.apache.lucene.store.NativeFSLockFactory@12cd8c11; 
> maxCacheMB=48.0 maxMergeSizeMB=4.0)",
> "segmentsFile":"segments_2z",
> "segmentsFileSizeInBytes":1947,
> "userData":{
>   "commitCommandVer":"0",
>   "commitTimeMSec":"1640647856055"},
> "lastModified":"2021-12-27T23:30:56.055Z",
> "sizeInBytes":1641346285,
> "size":"1.53 GB"}},
> "statistics":{
>   "name":"statistics",
>   "instanceDir":"/var/solr/data/statistics",
>   "dataDir":"/var/solr/data/statistics/data/",
>   "config":"solrconfig.xml",
>   "schema":"schema.xml",
>   "startTime":"2021-12-28T10:55:07.565Z",
>   "uptime":11864565,
>   "index":{
> "numDocs":78,
> "maxDoc":78,
> "deletedDocs":0,
> "indexHeapUsageBytes":38772,
> "version":46,
> "segmentCount":11,
> "current":false,
> "hasDeletions":false,
> 
> "directory":"org.apache.lucene.store.NRTCachingDirectory:NRTCachingDirectory(MMapDirectory@/var/solr/data/statistics/data/index
>  
> lockFactory=org.ap

[dspace-tech] Re: A How-To Solr installation on Ubuntu servers

[Chris Clawson]

Thanks for revisiting this! There is detail here which I have never seen, 
especially step e) . I will probably attempt a removal/re-installation of 
Solr in a few hours. Here is the results of my status checks, using curl:
root@media:~# curl http://localhost:8983/solr/admin/cores
{
  "responseHeader":{
"status":0,
"QTime":70},
  "initFailures":{},
  "status":{}}
root@media:~# curl http://localhost:8983/solr/admin/cores?action=STATUS
{
  "responseHeader":{
"status":0,
"QTime":1},
  "initFailures":{},
  "status":{}}
root@media:~#

... I don't see any DSpace names mentioned in these returns, so I am 
guessing there is an issue here.

On Tuesday, December 28, 2021 at 7:41:15 AM UTC-5 Mohammad S. AlMutairi 
wrote:

> A lot of newcomers who want to try DSpace specially non-technical people 
> do face an issue installing Solr for DSpace. The DSpace Solr installation 
> portion doesn't cover specific details about any Linux OS so to make things 
> easier for the folks who are using Ubuntu I'm posting a detailed 
> instructions how Solr should be installed on Ubuntu in a hope someone who 
> deserve helping save his time and get Solr up and running in no time. See 
> Solr installation steps and also the removal of solr if you ever need to 
> remove it below. Hope it doesn't fire back as it did not long time ago!.
>
> # Solr Installation 
> #
> # set a password for the root user.
> sudo passwd root
>
> # login with root to start solr installation.
> su - root
>
> a) mkdir /build
> b) cd /build
> c) wget https://downloads.apache.org/lucene/solr/8.11.1/solr-8.11.1.tgz
> d) tar xzf solr-8.11.1.tgz solr-8.11.1/bin/install_solr_service.sh 
> --strip-components=2
> e) perl -i -pe 's/SOLR_USER=solr/SOLR_USER=tomcat/;' 
> /build/install_solr_service.sh
> f) bash ./install_solr_service.sh solr-8.11.1.tgz -f
> g) echo SOLR_OPTS=\"\$SOLR_OPTS 
> -Dsolr.allowPaths=/opt/dspace/solr/statistics,/opt/dspace/temp/solr-data\" 
> >> /etc/default/solr.in.sh
> h) cp -r /opt/dspace/solr/* /var/solr/data/ # Do this step after 
> installing dspace backend (REST API server). You need to change /opt/dspace 
> to the folder you installed dspace backend into.
> i) chown -R tomcat:tomcat /opt/sol*
> j) chown -R tomcat:tomcat /var/solr/data/
> k) systemctl enable solr
> l) systemctl restart solr
>
> # Run curl as you see it below to test Solr and check the status of dspace 
> cores you copied in step (h) above. Dspace cores names you should see and 
> see it's data are (authority, oai, search and statistics).
> curl http://localhost:8983/solr/admin/cores
> curl http://localhost:8983/solr/admin/cores?action=STATUS
>
> # End of Solr Installation 
> ##
>
> # Steps to manually uninstall Solr from Ubuntu 
> ##
> # You need to login with root.
> # login with root to remove old solr installation from your server.
> su - root
>
> 1) systemctl stop solr
> 2) rm -r /var/solr
> 3) rm -r /opt/sol*
> 4) rm /etc/init.d/solr
> 5) deluser --remove-home solr
> 6) deluser --group solr
> 7) update-rc.d -f solr remove
> 8) rm -rf /etc/default/solr.in.sh
> # End of Solr Removal instructions 
> ##
>
>
> "When the sage points at the moon, the fool looks at the finger"
>
>

-- 
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/4cd45117-bd78-4805-bb65-dd42740fdbaen%40googlegroups.com.

[dspace-tech] Re: Angular is up, but Cannot Login

[Chris Clawson]

Another Question: Below is the Rest portion of my environment.prods.ts file 
in /dspace-angular. I am using port 8443, rather than 443. Might this be 
causing all the 'CORS header ‘Access-Control-Allow-Origin’ missing). Status 
code: 403' messages?

  rest: {
  ssl: true,
  host: 'mywebsite.com',
  port: 8443,
  // NOTE: Space is capitalized because 'namespace' is a reserved 
string in TypeScript
  nameSpace: '/server'
  }

On Monday, December 27, 2021 at 7:36:51 PM UTC-5 Chris Clawson wrote:

> More reading led me to my Firefox debug console. There are messages, like 
> "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the 
> remote resource at https://myserver.com; all over the place. I still have 
> no idea what to do about it, but I guess this is where I keep studying..
>
> On Monday, December 27, 2021 at 3:41:04 PM UTC-5 Chris Clawson wrote:
>
>> First DSpace 7 Angular UI screen! – (but) Unable to log in.
>>
>> I would appreciate some guidance. I was just successful in getting a 
>> DSpace 7 welcome screen from my remote webserver. I am unable to log in or 
>> browse the default database . Below the home page search box (Search the 
>> repository) is a message which says “error.top-level-communites “. If I 
>> click on any of the top menus (Communities, Statistics, etc) the screen 
>> attempts to load the page and then hangs (… loading..), as if waiting 
>> forever. I have added two Epersons and an Administrator using the ./dspace 
>> command line utility and am able to list them back, but the ui login says 
>> “invalid email or password”. So far, any command line database utility I 
>> have attempted has worked. The default database seems to be there 
>> (including my own two added epersons), but the ui doesn't appear to be 
>> accessing it. (right?)
>>
>> I had earlier issues installing Solr. Solr is running now as user 'solr'. 
>> The installation directories in /opt are owned by 'root', but the 
>> /server/solr/configsets are owned by 'solr'. When I try and run the command 
>> './dspace solr-reindex-statistics' I get an error: 
>>
>> Exception: Error from server at http://localhost:8983/solr: Path 
>> /dspace/solr/statistics must be relative to SOLR_HOME, SOLR_DATA_HOME 
>> coreRootDirectory. Set system property 'solr.allowPaths' to add other 
>> allowed paths.
>>
>> ?? Is this related to my primary problem? Where are these paths defined 
>> (SOLR_HOME, SOLR_DATA_HOME, etc)? I didn't see them in dspace.cfg or 
>> local.cfg.
>>
>> Some help in guiding the blind would be appreciated, here!
>>
>> Chris
>>
>>
>> Ubuntu 18.04
>>
>> KVM Cloud server
>>
>> 2 cpu cores 
>>
>> 4GB ram
>>
>

-- 
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/8709374b-8790-441b-af1f-259be8fd93d1n%40googlegroups.com.

[dspace-tech] Re: Angular is up, but Cannot Login

[Chris Clawson]

More reading led me to my Firefox debug console. There are messages, like 
"Cross-Origin Request Blocked: The Same Origin Policy disallows reading the 
remote resource at https://myserver.com; all over the place. I still have 
no idea what to do about it, but I guess this is where I keep studying..

On Monday, December 27, 2021 at 3:41:04 PM UTC-5 Chris Clawson wrote:

> First DSpace 7 Angular UI screen! – (but) Unable to log in.
>
> I would appreciate some guidance. I was just successful in getting a 
> DSpace 7 welcome screen from my remote webserver. I am unable to log in or 
> browse the default database . Below the home page search box (Search the 
> repository) is a message which says “error.top-level-communites “. If I 
> click on any of the top menus (Communities, Statistics, etc) the screen 
> attempts to load the page and then hangs (… loading..), as if waiting 
> forever. I have added two Epersons and an Administrator using the ./dspace 
> command line utility and am able to list them back, but the ui login says 
> “invalid email or password”. So far, any command line database utility I 
> have attempted has worked. The default database seems to be there 
> (including my own two added epersons), but the ui doesn't appear to be 
> accessing it. (right?)
>
> I had earlier issues installing Solr. Solr is running now as user 'solr'. 
> The installation directories in /opt are owned by 'root', but the 
> /server/solr/configsets are owned by 'solr'. When I try and run the command 
> './dspace solr-reindex-statistics' I get an error: 
>
> Exception: Error from server at http://localhost:8983/solr: Path 
> /dspace/solr/statistics must be relative to SOLR_HOME, SOLR_DATA_HOME 
> coreRootDirectory. Set system property 'solr.allowPaths' to add other 
> allowed paths.
>
> ?? Is this related to my primary problem? Where are these paths defined 
> (SOLR_HOME, SOLR_DATA_HOME, etc)? I didn't see them in dspace.cfg or 
> local.cfg.
>
> Some help in guiding the blind would be appreciated, here!
>
> Chris
>
>
> Ubuntu 18.04
>
> KVM Cloud server
>
> 2 cpu cores 
>
> 4GB ram
>

-- 
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/7a32907a-505d-4e34-a400-0580b30c2a59n%40googlegroups.com.

[dspace-tech] Angular is up, but Cannot Login

[Chris Clawson]

 

First DSpace 7 Angular UI screen! – (but) Unable to log in.

I would appreciate some guidance. I was just successful in getting a DSpace 
7 welcome screen from my remote webserver. I am unable to log in or browse 
the default database . Below the home page search box (Search the 
repository) is a message which says “error.top-level-communites “. If I 
click on any of the top menus (Communities, Statistics, etc) the screen 
attempts to load the page and then hangs (… loading..), as if waiting 
forever. I have added two Epersons and an Administrator using the ./dspace 
command line utility and am able to list them back, but the ui login says 
“invalid email or password”. So far, any command line database utility I 
have attempted has worked. The default database seems to be there 
(including my own two added epersons), but the ui doesn't appear to be 
accessing it. (right?)

I had earlier issues installing Solr. Solr is running now as user 'solr'. 
The installation directories in /opt are owned by 'root', but the 
/server/solr/configsets are owned by 'solr'. When I try and run the command 
'./dspace solr-reindex-statistics' I get an error: 

Exception: Error from server at http://localhost:8983/solr: Path 
/dspace/solr/statistics must be relative to SOLR_HOME, SOLR_DATA_HOME 
coreRootDirectory. Set system property 'solr.allowPaths' to add other 
allowed paths.

?? Is this related to my primary problem? Where are these paths defined 
(SOLR_HOME, SOLR_DATA_HOME, etc)? I didn't see them in dspace.cfg or 
local.cfg.

Some help in guiding the blind would be appreciated, here!

Chris


Ubuntu 18.04

KVM Cloud server

2 cpu cores 

4GB ram

-- 
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/72d81c33-a6dc-4eb2-af6e-f29de0cb0696n%40googlegroups.com.

[dspace-tech] Re: Status: DSpace 7.1 installation - What 'solr' group/user? Where?

[Chris Clawson]

Thanks for the help! I already understand that the system startup script is 
in /etc/init.d . The problem now seems to be that the full service of Solr 
(extracted in /build) contains the tar (package file) and the 
install_solr_service.sh script, which you have said to modify for user 
'tomcat' (instead of 'solr'). Changing this username causes the 
installation to fail as a service, although you can start solr manually out 
of the /opt/solr/bin directory (which I understand you should not do.
I need to explore why the installation script works with user 'solr', and 
then fails if I try a clean install as 'tomcat'. Maybe I can play with 
group permissions and use the 'solr' user, while permitting the 'tomcat' 
user to have access permissions to the solr group (as well as my DSpace 
directory). Unless anyone replies more here, I will end this thread and 
start a new one later. I might start the conversation fresh with a new 
summary and the benefit of what I have learned. You have help much in 
learning where to look. Thanks!

On Tuesday, December 21, 2021 at 5:43:15 PM UTC-5 Mohammad S. AlMutairi 
wrote:

> Chris,
>
> Re-reading your message made me understand the confusion you have. Please 
> don't start solr from /opt/solr-8.11.1/bin ... The solr startup script in 
> ubuntu is located here /etc/init.d/solr ... If you edit this file you will 
> see in line 56 solr will be run as tomcat and more thing please use 
> systemctl start solr to run it or systemctl enable solr to enable it at 
> boot time and so on...
>
> (( I understand 'install_solr_service.sh' needs to have the username 
> changed from 'solr' to my actual DSpace user 'tomcat', but you are saying 
> this script appears in '/etc/default/install_solr_service.sh' . Before 
> installation, the only place it appears is in /build . This was where I 
> edited 'install_solr_service.sh'. Once this script is run, my installation 
> directory is '/opt/solr-8.11.1' and the script (original and unedited from 
> the tar archive) is written to '/opt/solr-8.11.1/bin' . Of course, the 
> default 'SOLR_USER=solr' rather than 'tomcat' is there. Is this script in 
> it's new location important to edit 'SOLR_USER=' to 'tomcat as well? What 
> about this path to ' /etc/default/install_solr_service.sh'? The only thing 
> (solr) at '/etc/default/' is 'solr.in.sh', which doesn't seem to be 
> involved with defining users.))
>
>
> Mohammed
> On Tuesday, December 21, 2021 at 9:03:00 PM UTC+3 Chris Clawson wrote:
>
>> Mohammad -
>> I am attempting a fresh Solr install as per you detailed instructions. 
>> The first attempt now has a functional solr, but won't start as a service 
>> at run time. I can force start solr as user 'tomcat' by the command 'sudo 
>> -u tomcat ./solr start' from the  /opt/solr-8.11.1/bin directory. I was 
>> then able to connect to Solr at http://meloware.com:8983/solr/#/ , but I 
>> get an error "Error code: SSL_ERROR_RX_RECORD_TOO_LONG" when I attempt to 
>> connect to https://meloware.com:8983/solr/#/  . Maybe I am not supposed 
>> to do that, even on good days.
>>
>> Without more help, I will probably try and clean/re-install solr-8.1.11 
>> again, but I should get some clarification about the instructions posted 
>> earlier in this thread.
>> Item (e) says to:
>>  vi ./install_solr_service.sh # You need to change SOLR_USER=solr to 
>> SOLR_USER=tomcat in /etc/default/install_solr_service.sh file. tomcat is 
>> the user which has write permission over dspace folder if not replace 
>> tomcat with the user you picked for dspace.
>>
>> I understand 'install_solr_service.sh' needs to have the username changed 
>> from 'solr' to my actual DSpace user 'tomcat', but you are saying this 
>> script appears in '/etc/default/install_solr_service.sh' . Before 
>> installation, the only place it appears is in /build . This was where I 
>> edited 'install_solr_service.sh'. Once this script is run, my installation 
>> directory is '/opt/solr-8.11.1' and the script (original and unedited from 
>> the tar archive) is written to '/opt/solr-8.11.1/bin' . Of course, the 
>> default 'SOLR_USER=solr' rather than 'tomcat' is there. Is this script in 
>> it's new location important to edit 'SOLR_USER=' to 'tomcat as well? What 
>> about this path to ' /etc/default/install_solr_service.sh'? The only thing 
>> (solr) at '/etc/default/' is 'solr.in.sh', which doesn't seem to be 
>> involved with defining users.
>> ***
>> I may have goofed somewhere and will try a clean re-install again. I 
>> still would appreciate the answers to three questions:
>> 1) Is the https error ' SSL_ERROR_RX_RECORD_TOO_LONG' something to worry 
>> about now or later? 
>> 2) S

[dspace-tech] Re: Status: DSpace 7.1 installation - What 'solr' group/user? Where?

[Chris Clawson]

The install_solr_service.sh script in /build fails when I have the user set 
to 'tomcat'. The service installs correctly is I leave the SOLR_USER as 
'solr'. My tomcat seems correctly installed and does load with system 
startup.
Might you clarify why I cannot install using this script, after I change 
the user to 'tomcat'?

On Tuesday, December 21, 2021 at 5:03:48 PM UTC-5 Mohammad S. AlMutairi 
wrote:

> Hello Chris,
>
> Enabling services so it will be started at boot time is straight forward. 
> To enable tomcat9 ( sudo systemctl enable tomcat9 ) to start it use ( sudo 
> systemctl start tomcat9 ) to check it's status use ( sudo systemctl status 
> tomcat9 ) to stop it use ( sudo systemctl stop tomcat9 ). replace tomcat9 
> with solr for the solr service and apache2 for the apache webserver.
>
> Here is the answer to your questions and please pardon me because I'm 
> struggling with my english.
> 1) You shouldn't worry about the SSL certificate error because Solr admin 
> should not be publicly accessible unless it's protected besides dspace 
> doesn't work if solr is password protected so to satisfy both requirements 
> Solr should be restricted to run on the loopback adapter (localhost) and 
> that's where dspace be default expect solr to be ( solr.server = 
> http://localhost:8983/solr ). You can test locally using wget or curl ( 
> curl http://localhost:8983/solr/ ) or you can setup a reverse proxy to 
> reach it and then you can use the browser for testing purposes but you have 
> to disable it afterwards. 
>
> 2) Sorry about that. It was a typo. I posted yesterday while in a hurry so 
> please ignore it. The solr installation script you should edit and changed 
> is what we extracted from the gzipped tar file in step (d) in the build 
> directory. You can skip step (e) and use the below perl command to change 
> the file without having to manuallt edit it.
>  * perl -i -pe 's/SOLR_USER=solr/SOLR_USER=tomcat/;' 
> /build/install_solr_service.sh
>
> 3) You don't need to unless you loose the changed installation script from 
> the build directory and you need to reinstall solr again.
>
> Mohammed
>
> On Tuesday, December 21, 2021 at 9:03:00 PM UTC+3 Chris Clawson wrote:
>
>> Mohammad -
>> I am attempting a fresh Solr install as per you detailed instructions. 
>> The first attempt now has a functional solr, but won't start as a service 
>> at run time. I can force start solr as user 'tomcat' by the command 'sudo 
>> -u tomcat ./solr start' from the  /opt/solr-8.11.1/bin directory. I was 
>> then able to connect to Solr at http://meloware.com:8983/solr/#/ , but I 
>> get an error "Error code: SSL_ERROR_RX_RECORD_TOO_LONG" when I attempt to 
>> connect to https://meloware.com:8983/solr/#/  . Maybe I am not supposed 
>> to do that, even on good days.
>>
>> Without more help, I will probably try and clean/re-install solr-8.1.11 
>> again, but I should get some clarification about the instructions posted 
>> earlier in this thread.
>> Item (e) says to:
>>  vi ./install_solr_service.sh # You need to change SOLR_USER=solr to 
>> SOLR_USER=tomcat in /etc/default/install_solr_service.sh file. tomcat is 
>> the user which has write permission over dspace folder if not replace 
>> tomcat with the user you picked for dspace.
>>
>> I understand 'install_solr_service.sh' needs to have the username changed 
>> from 'solr' to my actual DSpace user 'tomcat', but you are saying this 
>> script appears in '/etc/default/install_solr_service.sh' . Before 
>> installation, the only place it appears is in /build . This was where I 
>> edited 'install_solr_service.sh'. Once this script is run, my installation 
>> directory is '/opt/solr-8.11.1' and the script (original and unedited from 
>> the tar archive) is written to '/opt/solr-8.11.1/bin' . Of course, the 
>> default 'SOLR_USER=solr' rather than 'tomcat' is there. Is this script in 
>> it's new location important to edit 'SOLR_USER=' to 'tomcat as well? What 
>> about this path to ' /etc/default/install_solr_service.sh'? The only thing 
>> (solr) at '/etc/default/' is 'solr.in.sh', which doesn't seem to be 
>> involved with defining users.
>> ***
>> I may have goofed somewhere and will try a clean re-install again. I 
>> still would appreciate the answers to three questions:
>> 1) Is the https error ' SSL_ERROR_RX_RECORD_TOO_LONG' something to worry 
>> about now or later? 
>> 2) Should I presume the correct location to edit the 
>> 'install_solr_service.sh' script (for changing the SOLR_USER to 'tomcat')  
>> is the one in '/build' , and not in ' /etc/default/' ?
>> 3) Once installed, should I also edit 

[dspace-tech] Re: Status: DSpace 7.1 installation - What 'solr' group/user? Where?

[Chris Clawson]

OOPS - forgot!
I remember now that the installation script failed with:

Service solr installed.
Customize Solr startup configuration in /etc/default/solr.in.sh
Job for solr.service failed because the control process exited with error 
code.
See "systemctl status solr.service" and "journalctl -xe" for details.
● solr.service - LSB: Controls Apache Solr as a Service
   Loaded: loaded (/etc/init.d/solr; generated)
   Active: failed (Result: exit-code) since Tue 2021-12-21 12:39:44 CST; 5s 
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 3772 ExecStart=/etc/init.d/solr start (code=exited, 
status=1/FAILURE)
 Main PID: 1738 (code=exited, status=0/SUCCESS)

Dec 21 12:39:44 media systemd[1]: Starting LSB: Controls Apache Solr as a 
Service...
Dec 21 12:39:44 media su[3774]: Successful su for tomcat by root
Dec 21 12:39:44 media su[3774]: + ??? root:tomcat
Dec 21 12:39:44 media su[3774]: pam_unix(su:session): session opened for 
user tomcat by (uid=0)
Dec 21 12:39:44 media su[3774]: pam_unix(su:session): session closed for 
user tomcat
Dec 21 12:39:44 media systemd[1]: solr.service: Control process exited, 
code=exited status=1
Dec 21 12:39:44 media systemd[1]: solr.service: Failed with result 
'exit-code'.
Dec 21 12:39:44 media systemd[1]: Failed to start LSB: Controls Apache Solr 
as a Service.

I (sort of) see where to look to investigate this.  I am guessing I need to 
read up on 'LSB'. Might this problem be permission related?
On Tuesday, December 21, 2021 at 1:03:00 PM UTC-5 Chris Clawson wrote:

> Mohammad -
> I am attempting a fresh Solr install as per you detailed instructions. The 
> first attempt now has a functional solr, but won't start as a service at 
> run time. I can force start solr as user 'tomcat' by the command 'sudo -u 
> tomcat ./solr start' from the  /opt/solr-8.11.1/bin directory. I was then 
> able to connect to Solr at http://meloware.com:8983/solr/#/ , but I get 
> an error "Error code: SSL_ERROR_RX_RECORD_TOO_LONG" when I attempt to 
> connect to https://meloware.com:8983/solr/#/  . Maybe I am not supposed 
> to do that, even on good days.
>
> Without more help, I will probably try and clean/re-install solr-8.1.11 
> again, but I should get some clarification about the instructions posted 
> earlier in this thread.
> Item (e) says to:
>  vi ./install_solr_service.sh # You need to change SOLR_USER=solr to 
> SOLR_USER=tomcat in /etc/default/install_solr_service.sh file. tomcat is 
> the user which has write permission over dspace folder if not replace 
> tomcat with the user you picked for dspace.
>
> I understand 'install_solr_service.sh' needs to have the username changed 
> from 'solr' to my actual DSpace user 'tomcat', but you are saying this 
> script appears in '/etc/default/install_solr_service.sh' . Before 
> installation, the only place it appears is in /build . This was where I 
> edited 'install_solr_service.sh'. Once this script is run, my installation 
> directory is '/opt/solr-8.11.1' and the script (original and unedited from 
> the tar archive) is written to '/opt/solr-8.11.1/bin' . Of course, the 
> default 'SOLR_USER=solr' rather than 'tomcat' is there. Is this script in 
> it's new location important to edit 'SOLR_USER=' to 'tomcat as well? What 
> about this path to ' /etc/default/install_solr_service.sh'? The only thing 
> (solr) at '/etc/default/' is 'solr.in.sh', which doesn't seem to be 
> involved with defining users.
> ***
> I may have goofed somewhere and will try a clean re-install again. I still 
> would appreciate the answers to three questions:
> 1) Is the https error ' SSL_ERROR_RX_RECORD_TOO_LONG' something to worry 
> about now or later? 
> 2) Should I presume the correct location to edit the 
> 'install_solr_service.sh' script (for changing the SOLR_USER to 'tomcat')  
> is the one in '/build' , and not in ' /etc/default/' ?
> 3) Once installed, should I also edit  SOLR_USER  in  
> '/opt/solr-8.11.1/bin/install_solr_service.sh' and also change that 
> variable to 'tomcat', as I first did with the script in /build?
> Thanks - I'll 'get it' eventually
> On Monday, December 20, 2021 at 9:17:06 PM UTC-5 Mohammad S. AlMutairi 
> wrote:
>
>> You most welcome. Let us here in group how it goes or if you need help 
>> with what's left to get it up and running. Good luck.
>>
>> On Tuesday, December 21, 2021 at 1:51:00 AM UTC+3 Chris Clawson wrote:
>>
>>> I just took a better look at Mohammad's excellent, detailed 
>>> instructions. Rather than proceeding with the front-end installation, I 
>>> think I will make a re-install of Solr 8.11.1 as per his instructions. 
>>> Thanks for the great detail!
>>>
>>> On Monday, December 20, 2021 at 5:42:26 PM UTC-5 Chris Clawson wrote:
>>>
>>>&

[dspace-tech] Status: DSpace 7.1 installation - What 'solr' group/user? Where?

[Chris Clawson]

Mohammad -
I am attempting a fresh Solr install as per you detailed instructions. The 
first attempt now has a functional solr, but won't start as a service at 
run time. I can force start solr as user 'tomcat' by the command 'sudo -u 
tomcat ./solr start' from the  /opt/solr-8.11.1/bin directory. I was then 
able to connect to Solr at http://meloware.com:8983/solr/#/ , but I get an 
error "Error code: SSL_ERROR_RX_RECORD_TOO_LONG" when I attempt to connect 
to https://meloware.com:8983/solr/#/  . Maybe I am not supposed to do that, 
even on good days.

Without more help, I will probably try and clean/re-install solr-8.1.11 
again, but I should get some clarification about the instructions posted 
earlier in this thread.
Item (e) says to:
 vi ./install_solr_service.sh # You need to change SOLR_USER=solr to 
SOLR_USER=tomcat in /etc/default/install_solr_service.sh file. tomcat is 
the user which has write permission over dspace folder if not replace 
tomcat with the user you picked for dspace.

I understand 'install_solr_service.sh' needs to have the username changed 
from 'solr' to my actual DSpace user 'tomcat', but you are saying this 
script appears in '/etc/default/install_solr_service.sh' . Before 
installation, the only place it appears is in /build . This was where I 
edited 'install_solr_service.sh'. Once this script is run, my installation 
directory is '/opt/solr-8.11.1' and the script (original and unedited from 
the tar archive) is written to '/opt/solr-8.11.1/bin' . Of course, the 
default 'SOLR_USER=solr' rather than 'tomcat' is there. Is this script in 
it's new location important to edit 'SOLR_USER=' to 'tomcat as well? What 
about this path to ' /etc/default/install_solr_service.sh'? The only thing 
(solr) at '/etc/default/' is 'solr.in.sh', which doesn't seem to be 
involved with defining users.
***
I may have goofed somewhere and will try a clean re-install again. I still 
would appreciate the answers to three questions:
1) Is the https error ' SSL_ERROR_RX_RECORD_TOO_LONG' something to worry 
about now or later? 
2) Should I presume the correct location to edit the 
'install_solr_service.sh' script (for changing the SOLR_USER to 'tomcat')  
is the one in '/build' , and not in ' /etc/default/' ?
3) Once installed, should I also edit  SOLR_USER  in  
'/opt/solr-8.11.1/bin/install_solr_service.sh' and also change that 
variable to 'tomcat', as I first did with the script in /build?
Thanks - I'll 'get it' eventually
On Monday, December 20, 2021 at 9:17:06 PM UTC-5 Mohammad S. AlMutairi 
wrote:

> You most welcome. Let us here in group how it goes or if you need help 
> with what's left to get it up and running. Good luck.
>
> On Tuesday, December 21, 2021 at 1:51:00 AM UTC+3 Chris Clawson wrote:
>
>> I just took a better look at Mohammad's excellent, detailed instructions. 
>> Rather than proceeding with the front-end installation, I think I will make 
>> a re-install of Solr 8.11.1 as per his instructions. Thanks for the great 
>> detail!
>>
>> On Monday, December 20, 2021 at 5:42:26 PM UTC-5 Chris Clawson wrote:
>>
>>> Gentlemen, Thank you.
>>>
>>> I am sorry about not including my system conditions (I normally do 
>>> include them). I am not an I.T. professional and cannot follow directions 
>>> by nature. I am running a KVM container with Ubuntu 18.?, LAMP and Tomcat 
>>> 9. I don't remember how I installed the packages, but although I could 
>>> manually start them,  I couldn't get them to to load/run at boot time. It 
>>> took a day or more for me to discover there was a difference between 
>>> systemd and init.d. (An important one.) I now have both Tomcat and Solr 
>>> running as systemd services and I have created a user/group 'solr' 
>>> *without* any password assigned to the Solr user. PLEASE let me know if 
>>> there is something to fix at this point. The DSpace seems to start fine at 
>>> boot time, now. I also have just finished installing SSL for both Apache 
>>> and Tomcat. My back-end Hal browser pages happily displays now when 
>>> accessing https://meloware.com:8443/#/api . I will copy and save the 
>>> valuable information you have took the time to mention here and save it for 
>>> future reference. This site is practice before attempting to upgrade my 
>>> production server (with DSpace 6.3) at https://montaguearchive.org:8443/ 
>>> .
>>> Chris
>>>
>>> On Monday, December 20, 2021 at 12:56:31 PM UTC-5 Mohammad S. AlMutairi 
>>> wrote:
>>>
>>>> Hello Chris,
>>>>
>>>> You dropped a vital piece of information about the Linux flavor you are 
>>>> using so I'm assuming a Debian derivative. It's better to start a fresh 
>>>> Solr installat

[dspace-tech] Re: DSpace 7.1 installation - What 'solr' group/user? Where?

[Chris Clawson]

I just took a better look at Mohammad's excellent, detailed instructions. 
Rather than proceeding with the front-end installation, I think I will make 
a re-install of Solr 8.11.1 as per his instructions. Thanks for the great 
detail!

On Monday, December 20, 2021 at 5:42:26 PM UTC-5 Chris Clawson wrote:

> Gentlemen, Thank you.
>
> I am sorry about not including my system conditions (I normally do include 
> them). I am not an I.T. professional and cannot follow directions by 
> nature. I am running a KVM container with Ubuntu 18.?, LAMP and Tomcat 9. I 
> don't remember how I installed the packages, but although I could manually 
> start them,  I couldn't get them to to load/run at boot time. It took a day 
> or more for me to discover there was a difference between systemd and 
> init.d. (An important one.) I now have both Tomcat and Solr running as 
> systemd services and I have created a user/group 'solr' *without* any 
> password assigned to the Solr user. PLEASE let me know if there is 
> something to fix at this point. The DSpace seems to start fine at boot 
> time, now. I also have just finished installing SSL for both Apache and 
> Tomcat. My back-end Hal browser pages happily displays now when accessing 
> https://meloware.com:8443/#/api . I will copy and save the valuable 
> information you have took the time to mention here and save it for future 
> reference. This site is practice before attempting to upgrade my production 
> server (with DSpace 6.3) at https://montaguearchive.org:8443/ .
> Chris
>
> On Monday, December 20, 2021 at 12:56:31 PM UTC-5 Mohammad S. AlMutairi 
> wrote:
>
>> Hello Chris,
>>
>> You dropped a vital piece of information about the Linux flavor you are 
>> using so I'm assuming a Debian derivative. It's better to start a fresh 
>> Solr installation by removing the old Solr installation and following the 
>> steps you see below.
>>
>> a) mkdir /build
>> b) cd /build
>> c) wget https://downloads.apache.org/lucene/solr/8.11.1/solr-8.11.1.tgz
>> d) tar xzf solr-8.11.1.tgz solr-8.11.1/bin/install_solr_service.sh 
>> --strip-components=2
>> e) vi ./install_solr_service.sh # You need to change SOLR_USER=solr to 
>> SOLR_USER=tomcat in /etc/default/install_solr_service.sh file. tomcat is 
>> the user which has write permission over dspace folder if not replace 
>> tomcat with the user you picked for dspace.
>> f) bash ./install_solr_service.sh solr-8.11.1.tgz
>> g) vi /etc/default/solr.in.sh # You need to add dspace folders in Solr 
>> allowed paths.
>> SOLR_OPTS="$SOLR_OPTS 
>> -Dsolr.allowPaths=/opt/dspace/solr/statistics,/opt/dspace/temp/solr-data"
>> h) cp -r /opt/dspace/solr/* /var/solr/data/ # Do this step after 
>> installing dspace. You need to change /opt/dspace to the folder you 
>> installed dspace into.
>> i) chown -R tomcat:tomcat /var/solr/data/ # You need to change the user 
>> and the group if it differs from the user and group you chose for dspace.
>> j) systemctl enable solr
>> k) systemctl restart solr
>>
>> *** You might fall into this issue at a later stage. Running 
>> /opt/dspace/bin/dspace solr-reindex-statistics for the first time will 
>> complain with the error message you see below but running it again will 
>> complete successfully ( I think the error shows up because of the existence 
>> of /opt/dspace/solr/statistics/core.properties file which gets deleted at 
>> the first run) .  Maybe Tim can shed some light on this.
>> ### error message ### Could not create a new core in 
>> /opt/dspace/solr/statistics as another core is already defined there ### 
>> end of error message ###
>>
>>  Steps to uninstall Solr on Ubuntu manually ##
>> systemctl stop solr
>> rm -r /var/solr
>> rm -r /opt/solr-8.x.x
>> rm -r /opt/solr
>> rm /etc/init.d/solr
>> deluser --remove-home solr
>> deluser --group solr
>> update-rc.d -f solr remove
>> rm -rf /etc/default/solr.in.sh
>> #
>>
>> Mohammed
>> On Monday, December 20, 2021 at 5:49:39 PM UTC+3 DSpace Technical Support 
>> wrote:
>>
>>> Hi Chris,
>>>
>>> The 'solr' user should be created by default when installing Apache 
>>> Solr.  In any case, Apache Solr recommends *not* running Solr as root.  
>>> Instead, they recommend creating a "solr" user (it could be named something 
>>> else if you want) to install Solr under.  
>>>
>>> See this Apache guide for taking Solr to production for more 
>>> information: 
>>> https://solr.apache.org/guide/8_1/t

[dspace-tech] Re: DSpace 7.1 installation - What 'solr' group/user? Where?

[Chris Clawson]

Gentlemen, Thank you.

I am sorry about not including my system conditions (I normally do include 
them). I am not an I.T. professional and cannot follow directions by 
nature. I am running a KVM container with Ubuntu 18.?, LAMP and Tomcat 9. I 
don't remember how I installed the packages, but although I could manually 
start them,  I couldn't get them to to load/run at boot time. It took a day 
or more for me to discover there was a difference between systemd and 
init.d. (An important one.) I now have both Tomcat and Solr running as 
systemd services and I have created a user/group 'solr' *without* any 
password assigned to the Solr user. PLEASE let me know if there is 
something to fix at this point. The DSpace seems to start fine at boot 
time, now. I also have just finished installing SSL for both Apache and 
Tomcat. My back-end Hal browser pages happily displays now when accessing 
https://meloware.com:8443/#/api . I will copy and save the valuable 
information you have took the time to mention here and save it for future 
reference. This site is practice before attempting to upgrade my production 
server (with DSpace 6.3) at https://montaguearchive.org:8443/ .
Chris

On Monday, December 20, 2021 at 12:56:31 PM UTC-5 Mohammad S. AlMutairi 
wrote:

> Hello Chris,
>
> You dropped a vital piece of information about the Linux flavor you are 
> using so I'm assuming a Debian derivative. It's better to start a fresh 
> Solr installation by removing the old Solr installation and following the 
> steps you see below.
>
> a) mkdir /build
> b) cd /build
> c) wget https://downloads.apache.org/lucene/solr/8.11.1/solr-8.11.1.tgz
> d) tar xzf solr-8.11.1.tgz solr-8.11.1/bin/install_solr_service.sh 
> --strip-components=2
> e) vi ./install_solr_service.sh # You need to change SOLR_USER=solr to 
> SOLR_USER=tomcat in /etc/default/install_solr_service.sh file. tomcat is 
> the user which has write permission over dspace folder if not replace 
> tomcat with the user you picked for dspace.
> f) bash ./install_solr_service.sh solr-8.11.1.tgz
> g) vi /etc/default/solr.in.sh # You need to add dspace folders in Solr 
> allowed paths.
> SOLR_OPTS="$SOLR_OPTS 
> -Dsolr.allowPaths=/opt/dspace/solr/statistics,/opt/dspace/temp/solr-data"
> h) cp -r /opt/dspace/solr/* /var/solr/data/ # Do this step after 
> installing dspace. You need to change /opt/dspace to the folder you 
> installed dspace into.
> i) chown -R tomcat:tomcat /var/solr/data/ # You need to change the user 
> and the group if it differs from the user and group you chose for dspace.
> j) systemctl enable solr
> k) systemctl restart solr
>
> *** You might fall into this issue at a later stage. Running 
> /opt/dspace/bin/dspace solr-reindex-statistics for the first time will 
> complain with the error message you see below but running it again will 
> complete successfully ( I think the error shows up because of the existence 
> of /opt/dspace/solr/statistics/core.properties file which gets deleted at 
> the first run) .  Maybe Tim can shed some light on this.
> ### error message ### Could not create a new core in 
> /opt/dspace/solr/statistics as another core is already defined there ### 
> end of error message ###
>
>  Steps to uninstall Solr on Ubuntu manually ##
> systemctl stop solr
> rm -r /var/solr
> rm -r /opt/solr-8.x.x
> rm -r /opt/solr
> rm /etc/init.d/solr
> deluser --remove-home solr
> deluser --group solr
> update-rc.d -f solr remove
> rm -rf /etc/default/solr.in.sh
> #
>
> Mohammed
> On Monday, December 20, 2021 at 5:49:39 PM UTC+3 DSpace Technical Support 
> wrote:
>
>> Hi Chris,
>>
>> The 'solr' user should be created by default when installing Apache 
>> Solr.  In any case, Apache Solr recommends *not* running Solr as root.  
>> Instead, they recommend creating a "solr" user (it could be named something 
>> else if you want) to install Solr under.  
>>
>> See this Apache guide for taking Solr to production for more information: 
>> https://solr.apache.org/guide/8_1/taking-solr-to-production.html#create-the-solr-user
>>   
>>  That guide is also linked to from the main "Installing Solr" instructions 
>> in the "Preparing for Installation" section: 
>> https://solr.apache.org/guide/8_1/installing-solr.html#preparing-for-installation
>>
>> Hopefully that helps explain things better!
>>
>> Tim
>>
>> On Saturday, December 18, 2021 at 11:16:07 AM UTC-6 Chris Clawson wrote:
>>
>>> I have Solr 8.11.1 extracted to /opt/solr-8.11.1 . The command line 
>>> example (provided in the Apache Foundation quick start instructions), 
>>>  ./bin/solr start -e

[dspace-tech] DSpace 7.1 installation - What 'solr' group/user? Where?

[Chris Clawson]

I have Solr 8.11.1 extracted to /opt/solr-8.11.1 . The command line example 
(provided in the Apache Foundation quick start instructions),  ./bin/solr 
start -e cloud , produces a 'welcome' message.
Step #13 of the DSpace 7.x installation page instructs me to copy dspace 
configsets to the installed Solr directory. (Fine.)
The second part of step #13 is telling me to change the group/owner of 
these configsets to 'solr':
chown -R solr:solr /opt/solr-8.11.1/server/solr/configsets
What group/user solr is this? It is not defined anywhere that I can find, 
and the Apache Foundation doesn't mention it anywhere I can see or 
understand.
Right now, the entire Solr directory is group and user owned by root:root. 
My DSpace operating system user will be 'tomcat'.

Please explain how and why I should use this 'solr' user and group. 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/4c7b24e7-f8c0-4b4d-9387-7f4aa54ad237n%40googlegroups.com.

Re: [dspace-tech] any organization to use DSpace 7

[Chris Clawson]

Yes -
I have begun to study if I am capable of upgrading a production 
installation of DSpace 6.3 to 7.1. My first effort will be a clean install 
on another web server I have, which currently only has Apache (for http) 
running. Then I will attempt to upgrade a test server I have in my home 
network, which is a clone of my production database and 6.3 installed. If 
all goes well, I will then attempt an upgrade at 
https://montagurarchive.org . This is a local US historical society and I 
am not an I.T. professional. I am, however, the best qualified person a lay 
community organization might expect to be available for such work. Wish me 
luck.

On Friday, December 17, 2021 at 10:12:39 AM UTC-5 al...@vt.edu wrote:

> 4Science announced in 
> https://groups.google.com/g/dspace-community/c/ZRHaqxDMurg,
>
> Let's celebrate! First repository with #dspace7 
> .1 online today JEWLScholar 
> @MTSUNews  Middle Tennessee State 
> University by 4Science jewlscholar.mtsu.edu/home - tinyurl.com/tst6sh38.
>
> On Thursday, December 16, 2021 at 4:19:24 PM UTC-5 Carl Jones wrote:
>
>> On a similar note, I'm also curious if anyone is using 7.* in production 
>> yet (or who are planning to do so in the not-too-distant future)?
>>
>> Carl
>>
>>
>> Carl Jones
>>
>> MIT Libraries
>>
>> Information Technology Services
>>
>> Enterprise Systems
>>
>> Bldg. NE36-6101
>>
>> 105 Broadway 
>>
>> Cambridge, MA 02142
>>
>>
>> On Thu, Dec 16, 2021 at 9:08 AM Joshua Kim  wrote:
>>
>>> Hi all,
>>>
>>> University of Delaware Library is working on installing DSPace 7. Is 
>>> there any way I can look at the websites of other organizations using 
>>> DSpace 7?
>>>
>>> 
>>> Joshua Kim
>>> Web Developer, Library IT
>>> Library, Museums and Press
>>> University of Delaware
>>>
>>> -- 
>>> 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/CAOE6Kn6yChiYchRr9wyZzUQwBwUs2Abp8BOPnto1SQ1-HSbOsA%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>>

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

Re: [dspace-tech] Log4J Vulnerability

[Chris Clawson]

Tim, please clarify! What about DSpace 7?  I am making a fresh install of 
DSpace 7.1. The Apache Solr Security page says Solr 8.11.0 (the current 
release) is vulnerable to attack. Your reassurance seems to be specific to 
DSpace 6.3. Are we safe to make new installations with DSpace 7.1 (using 
Apache Solr 8.11.0)?

On Wednesday, December 15, 2021 at 1:10:03 AM UTC-5 antti@gmail.com 
wrote:

> Hi!
>
> Thank you Tim for the clarification! I appreciate the fast response, even 
> when there may be a lot of fires to put out! 
>
> Best regards,
> Antti
>
> On Tuesday, December 14, 2021 at 4:55:24 PM UTC+2 Tim Donohue wrote:
>
>> CVE-2019-17571 (which is different vulnerability only impacting log4j v1) 
>> should not impact DSpace 6 or below, as it requires that you are using the 
>> log4j SocketServer in your configuration.  DSpace 6 or below do NOT use 
>> this configuration of log4j v1, as we always use a FileAppender for 
>> logging, see for example: 
>> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/log4j.properties#L46
>>
>> My understanding is that CVE-2019-17571 would require a much different 
>> configuration, using a SocketAppender instead of a FileAppender, e.g. 
>> https://howtodoinjava.com/log4j/log4j-socketappender-and-socket-server-example/
>>
>> Therefore, as long as you haven't modified your log4j configuration in 
>> DSpace 6 or below to use a SocketAppender (this is unlikely), you should be 
>> safe from  CVE-2019-17571.
>>
>> Tim
>>
>> On Tuesday, December 14, 2021 at 4:44:32 AM UTC-6 antti@gmail.com 
>> wrote:
>>
>>> Hi!
>>>
>>> While dspace 5.x and 6.x are safe from the latest log4j -vulnerability, 
>>> this got my attention: 
>>> https://nsfocusglobal.com/apache-log4j-deserialization-remote-code-execution-cve-2019-17571-vulnerability-threat-alert/
>>> No updates in log4j v1.x mean no fix to this issue. Has anyone happened 
>>> to dig into this and see if this vulnerability affect DSpace? And if so, 
>>> any mitigations or means available to fix this issue?
>>>
>>> Thanks in advance! Keep up the good work everyone o/
>>>
>>> -- Antti
>>>
>>>
>>> On Monday, December 13, 2021 at 7:32:10 PM UTC+2 
>>> dale.p...@vanderbilt.edu wrote:
>>>
 It is part of v5,  but I believe the delivered version is ok since it 
 is pre-vunerability.

  

  

 -Dale

  

 *From:* dspac...@googlegroups.com  *On 
 Behalf Of *Sarah Butash
 *Sent:* Monday, December 13, 2021 10:55 AM
 *To:* dspac...@googlegroups.com
 *Subject:* [dspace-tech] Log4J Vulnerability

  

 Hello,

  

 Our Security team has asked us to follow up to determine if Log4J is a 
 part of the build of DSpace v5, which I believe it is.  Can you confirm? 
 Do 
 you have a mitigation strategy for this issue?

  

 Thank you!

 Sarah

  

 -- 

 Sarah Butash

 she / her

 Library Systems Analyst, OU Libraries

 Kresge Library, Room 227

 100 Library Drive, Rochester, MI  48309-4479

 Phone: 248-370-2368 <(248)%20370-2368>

  

  

 -- 
 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/CAGdTMArkg14tVF-b0i4UWS59dvJyOYNy6MtjO3NCdWpL4M285A%40mail.gmail.com
  
 
 .

>>>

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

[dspace-tech] Re: Direct DB access for critical data?

[Chris Clawson]

Well, I have discovered a very helpful discussion here: 
https://wiki.lyrasis.org/display/DSPACE/The+metadatavalue+table
It only cites some very limited examples. Does anyone have links or access 
to a discussion with examples which could return my description field?

On Tuesday, April 6, 2021 at 10:26:40 AM UTC-4 Chris Clawson wrote:

> I have a DSpace 6.3 installation I am trying to pair with a Wordpress 
> website, on the same public server. I am attempting to access DSpace 
> content to populate pages in Wordpress and have made some crude successes. 
>
> What I would like to do is to write AJAX applications using server side 
> queries (for Wordpress pages), written in PHP, to directly access the 
> DSpace database in Postgresql.
>
> The DSpace database tables are a mystery to me. I can list them, but can't 
> find my most critical data: Item titles, descriptions and handles.
>
> Could you please comment and hopefully point me to the correct DB tables 
> or how I might directly get this information from the Postgre server?
>

-- 
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/453554a3-46d5-4c1a-b39b-331ed98feaccn%40googlegroups.com.

[dspace-tech] Direct DB access for critical data?

[Chris Clawson]

 

I have a DSpace 6.3 installation I am trying to pair with a Wordpress 
website, on the same public server. I am attempting to access DSpace 
content to populate pages in Wordpress and have made some crude successes. 

What I would like to do is to write AJAX applications using server side 
queries (for Wordpress pages), written in PHP, to directly access the 
DSpace database in Postgresql.

The DSpace database tables are a mystery to me. I can list them, but can't 
find my most critical data: Item titles, descriptions and handles.

Could you please comment and hopefully point me to the correct DB tables or 
how I might directly get this information from the Postgre server?

-- 
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/aa1a74cd-21e7-4303-a32c-caf11d8310c5n%40googlegroups.com.

Re: [dspace-tech] Make clickable links in DSpace 6.3 news-xmlui.xml?

[Chris Clawson]

Perfect! Works fine.
I followed a half dozen tutorials. They were all far more complicated and 
none of them worked. Thanks for eliminating this headache!
Chris

On Saturday, December 5, 2020 at 2:50:19 PM UTC-5 bla...@umich.edu wrote:

> How about this:
>
> https://montaguearchive.org;>Return 
> Home
>
>
> If you add *?XML* to dspace URLs you can see the xml being fed to the xsl 
> that makes the html.  That might give you some more ideas.
>
> -Jose
>
> On Sat, Dec 5, 2020 at 12:57 PM Chris Clawson  
> wrote:
>
>> Sorry if this has been already answered.
>>
>> Is there a simple way to place a clickable link (like "Return Home") in 
>> the introductory paragraph, used as the DSpace home page, running with a 
>> default xmlui theme?
>> I am trying to edit and presume the proper place would be /[dspace 
>> home]/config/news-xmlui.xml
>>
>> I wish to link back to my wordpress site. If someone can present an 
>> example, then I want a clickable link to "https://montaguearchive.org; 
>> and the text might be a heading like " Return to Main Site".
>> Thanks
>>
>> -- 
>> All messages to this mailing list should adhere to the DuraSpace Code of 
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dspace-tech/588ebb5e-2b4a-4fc2-8a14-1c530c465863n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/dspace-tech/588ebb5e-2b4a-4fc2-8a14-1c530c465863n%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/848aa3a4-b5eb-4fb6-8914-d32e9325962bn%40googlegroups.com.

[dspace-tech] Make clickable links in DSpace 6.3 news-xmlui.xml?

[Chris Clawson]

Sorry if this has been already answered.

Is there a simple way to place a clickable link (like "Return Home") in the 
introductory paragraph, used as the DSpace home page, running with a 
default xmlui theme?
I am trying to edit and presume the proper place would be /[dspace 
home]/config/news-xmlui.xml

I wish to link back to my wordpress site. If someone can present an 
example, then I want a clickable link to "https://montaguearchive.org; and 
the text might be a heading like " Return to Main Site".
Thanks

-- 
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/588ebb5e-2b4a-4fc2-8a14-1c530c465863n%40googlegroups.com.

[dspace-tech] Export item handle for slideshow?

[Chris Clawson]

I have a wordpress site partnered with my DSpace 6.3. I wish to create a 
slideshow presentation on Wordpress, directly from my DSpace repository. I 
have a DSpace collection defined as the slide elements of my presentation.

*How can I export the collection metadata, so that the URI handle of each 
item is included*? Right now, I only see the collection's metadata export 
showing the collection's handle, which of course I already know. If I could 
get the item's handles included in the export, I might easily prepare a 
slideshow in Wordpress.

-- 
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/94b8a682-feee-44a9-a956-8866639a2886n%40googlegroups.com.

Re: [dspace-tech] Upgrade from Version 6.3

[Chris Clawson]

Hmmm.. It sounds like an upgrade is a one time deal, with no going back. 
That makes me glad I have a test server. The 'side by side' install sounds 
interesting, but this conversation doesn't provide any detail or links 
explaining how to do that. If that were practical, I was thinking DSpace 7 
might be installed alongside the live 6.3, and once everything was migrated 
properly on a Release version of 7, the 6.3 install might be retired. Is 
that a viable idea?

On Thursday, October 15, 2020 at 1:57:30 PM UTC-4 Mark H. Wood wrote:

> On Thu, Oct 15, 2020 at 12:25:35PM -0400, Jose Blanco wrote:
> > Mark, I have a related question. We want to bring up a clean instance of
> > dspace 7 on the same server that we use for production that runs 6.3. It
> > sounds from your response about that our issue would be:
> > 
> > 
> > *DSpace 7 requires JDK 11, and DSpace 6 may not run on 11, so if youwant 
> to
> > switch back and forth you may need both.*
> > 
> > So therefore it would not be possible to have a separate dspace 7 on the
> > production server that is running 6.3. I think the other things you
> > mentioned would not be a problem, since the dspace 7 would be a new clean
> > installation, and not an upgrade to 6.3. Does that make sense?
>
> It is possible to run them side-by-side in two different Tomcat
> instances under different JVMs. For example, on Gentoo Linux I've
> installed both the OpenJDK 8 and 11 "slots", as well as Tomcat 7 and
> 8.5 slots. The Tomcat startup script can be configured as to which
> JVM to use, so I can have a Tomcat 7 running on JDK 8 and a Tomcat 8.5
> (on different ports, of course!) running on JDK 11. The Gentoo Tomcat
> packages also include a tool to set up multiple instances of the same
> slot, and I could have done it that way.
>
> Your OS may provide similar facilities. Or you can rig up multiple
> Tomcat instances yourself.
>
> -- 
> Mark H. Wood
> Lead Technology Analyst
>
> University Library
> Indiana University - Purdue University Indianapolis
> 755 W. Michigan Street
> Indianapolis, IN 46202
> 317-274-0749 <(317)%20274-0749>
> www.ulib.iupui.edu
>

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

[dspace-tech] Upgrade from Version 6.3

[Chris Clawson]

I have a test server on my home network, which is a partial clone of my 
live webserver installation of 6.3. I am considering upgrading the test 
machine to 7 Beta 4.
The goal is to temporarily preserve the working 6.3 install, while 
upgrading the packages, like Java JDK, Ant, Maven, PostgreSQL, etc. This 
would be practice for an eventual upgrade of my live server.
Can a DSpace 6.3 install survive such a package upgrade?
Is it practical to attempt a DSpace Beta 4 upgrade on an existing database? 
(This is a test system - no real harm will occur if it breaks).
I am no I.T. pro, but I did build this home server, myself. You comment and 
guidance is welcome - thanks.

-- 
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/b3c990c3-9c70-4c66-a3af-6c2cacb815bfn%40googlegroups.com.

Re: [dspace-tech] Re: Can't produce Thumbnails!

[Chris Clawson]

Thank You.
This limit will affect the ability to generate thumbnails for larger file 
size bitstreams. Once I lowered my image resolution, I found it easier for 
the system to produce thumbnails. Got it. Memory related, and using the 
command you describe will raise the limit.

-- 
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/6cedcc5a-6237-4be2-a913-edebd78c6f7do%40googlegroups.com.

[dspace-tech] Re: Can't produce Thumbnails!

[Chris Clawson]

Okay- Maybe this has something to do with the large image pixel size 4000 x 
6000 of the jpgs. Where can I adjust the amount of memory available for the 
'dspace filter-media' command?

-- 
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/3e476a8a-337a-465b-af16-e4a2052009d0o%40googlegroups.com.

[dspace-tech] Can't produce Thumbnails!

[Chris Clawson]

DSpace 6.3
Ubuntu 18.04

I just imported 1440 items to my database, using SimplaArchiveFormat. This 
all seemed to work fine and the new items can be searched and viewed. The 
image bitstreams will display fine, when viewed.
I can't create thumbnails! I even attempted create a single thumbnail with 
/dspace/bin/dspace filter-media -i 123456789/3787

Shouldn't this work immediately after import? The command "free -m" tells 
me two thirds of my system memory is still available. 

root@melo3:~# /dspace/bin/dspace filter-media -i 123456789/3587
File: E-Wells-Co-7-11-2018.679.jpg.jpg
!!! OutOfMemoryError !!!
FILTERED: bitstream d95f9b7f-7484-4287-93cd-379dcddce34c (item: 
123456789/3587) and created 'E-Wells-Co-7-11-2018.679.jpg.jpg'
File: E-Wells-Co-7-11-2018.679.jpg.jpg
ERROR filtering, skipping bitstream #d95f9b7f-7484-4287-93cd-379dcddce34c 
java.io.IOException: Error: Header doesn't contain versioninfo
java.io.IOException: Error: Header doesn't contain versioninfo
at org.apache.pdfbox.pdfparser.PDFParser.parse(PDFParser.java:244)
at org.apache.pdfbox.pdmodel.PDDocument.load(PDDocument.java:966)
at org.apache.pdfbox.pdmodel.PDDocument.load(PDDocument.java:868)
at 
org.dspace.app.mediafilter.PDFBoxThumbnail.getDestinationStream(PDFBoxThumbnail.java:80)
at 
org.dspace.app.mediafilter.MediaFilterServiceImpl.processBitstream(MediaFilterServiceImpl.java:361)
at 
org.dspace.app.mediafilter.MediaFilterServiceImpl.filterBitstream(MediaFilterServiceImpl.java:287)
at 
org.dspace.app.mediafilter.MediaFilterServiceImpl.filterItem(MediaFilterServiceImpl.java:181)
at 
org.dspace.app.mediafilter.MediaFilterServiceImpl.applyFiltersItem(MediaFilterServiceImpl.java:159)
at 
org.dspace.app.mediafilter.MediaFilterCLITool.main(MediaFilterCLITool.java:315)
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)
root@melo3:~#

-- 
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/c81725d0-0b6a-4320-ac81-0ac9e747c37do%40googlegroups.com.

Re: [dspace-tech] Unpredictable bitstream upload from web forms

[Chris Clawson]

Thank you, Mark

That was a good lesson. My Tomcat username is "tomcat8" and I found root 
group/owner scattered around the /dspace/assetstore directories. I 
re-assigned recursively all the directories within 'assetstore' with the 
command *chown -R tomcat8:tomcat8 /dspace/assetstore*


-- 
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/fa5cb38c-f40f-4a5a-9897-4d11fac03e2e%40googlegroups.com.

[dspace-tech] Unpredictable bitstream upload from web forms

[Chris Clawson]

 

(continuing from thread “Upgrading Tomcat? “)

This is a rented KVM container I control remotely via SSH. The minimal 
Ubuntu 18.04 installation was installed by my control panel. I am on a 
rather steep learning curve and had to glean my understanding from many 
sources online. So, it was my error or misunderstanding which installed 
Tomcat 8. The installation is now live, so I wish to 'fix' it without 
breaking it.


Over all, everything seems very stable, except for the unpredictable 
behavior when I attempt to upload images or other files using the web 
interface. When I submit a new item, I get as far as the “Upload File(s)” 
step. The browse dialog works fine and I select my desired jpg image. The 
“Next” button then usually results with a “No such file or directory” 
error. I am including the Java stacktrace, in case anyone can suggest 
something from it. If you attempt this a number of times, it eventually 
accepts the submitted upload.


For now, I have given up on web form submission and am uploading everything 
directly via FTP, where the command line procedures and utilities work 
fine. 


So, help with this web-form bit-stream problem upload would be welcome. I 
use an updated Firefox browser and my partner is using Edge. We both see 
the same problem. This problem might also exist when trying to upload CSV 
spreadsheets or templates.


Thanks


On Tuesday, June 2, 2020 at 2:10:42 AM UTC-4, Alan Orth wrote:

Dear Chris,


For what it's worth I have been running DSpace 5 and 6 with Tomcat 7.0.x 
for several years so your issues are likely not due to having an older 
Tomcat—you might want to look into those issues more (start another thread 
on this mailing list describing them)! Also, the Apache Tomcat project has 
announced (long ago) that the 8.0.x series is superseded by the 8.5.x 
series¹. Lastly, I see that Ubuntu 18.04 ships Tomcat 8.5.x with its system 
package manager². How did you manage to get 8.0.x? Are you on Ubuntu 16.04 
perhaps?


Regards,


-- 
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/268029f2-8c02-4df0-8316-cadbbfdcdb5a%40googlegroups.com.
<>

[dspace-tech] Re: Upgrading Tomcat?

[Chris Clawson]

Thank you, Mark

You have answered some real concerns. I am only using binaries installed 
using apt. I was concerned that ant might have built DSpace with 
dependencies from the Tomcat installation. I will also be installing the 
Tomcat binary, using apt. I am not a very advanced Linux/Ubuntu user, but I 
can still explore directories and check configuration files.

On Monday, June 1, 2020 at 2:07:20 PM UTC-4, Chris Clawson wrote:
>
> My DSpace 6 installation is on a remote server, running Ubuntu 18.04. I 
> guess I goofed and installed Tomcat 8.0.37 instead of Tomcat 8.5. It works, 
> but with assorted issues which may be because of the older Tomcat. Could 
> you please suggest or link to a procedure to upgrade Tomcat, without 
> blowing my working configuration?
>

-- 
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/9a8468d2-28f7-48f4-b19b-f6ea8f34b291%40googlegroups.com.

[dspace-tech] Upgrading Tomcat?

[Chris Clawson]

My DSpace 6 installation is on a remote server, running Ubuntu 18.04. I 
guess I goofed and installed Tomcat 8.0.37 instead of Tomcat 8.5. It works, 
but with assorted issues which may be because of the older Tomcat. Could 
you please suggest or link to a procedure to upgrade Tomcat, without 
blowing my working configuration?

-- 
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/1c448753-19fc-44b0-927f-75112aa496da%40googlegroups.com.

Re: [dspace-tech] Confusion in defining Roles

[Chris Clawson]

Well,
I appreciate the timing of the reply, but am not thrilled at the answer. 
Okay - Make version 7 great and soon! Thanks.

In this case, I guess I will create a web submission form, which will 
include the item URI and suggested edits. I will then take approved, 
submitted forms and create a batch metadata import and make the changes 
(myself) as administrator.

I get the impression that DSpace is best partnered with a traditional 
website, which presents the curated galleries and mission activities. 
Linking the DSpace server with a companion Wordpress website will be able 
to facilitate this kind of feature, in some acceptable way. I look forward 
to a production release of DSpace 7 and wouldn't want a distraction over 
this issue.

-- 
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/c3d228db-23ed-4133-809c-67f9f576a527%40googlegroups.com.

[dspace-tech] Confusion in defining Roles

[Chris Clawson]

I wish to create a new e-person account in a DSpace 6 web server, who will 
have the ability to edit or submit new metadata for existing items in 
collections I have given him access to. All of these edits I wish to keep 
pending, subject to approval of myself or another main Administrator.
Is this possible? Simple? How? 
I know all of this can be pending approval for new items, but what about 
pending changes to existing ones? 

-- 
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/d67804d4-697d-49cb-b277-eb205f359ab8%40googlegroups.com.

[dspace-tech] Install DSpace 7 Beta1 on remote machine?

[Chris Clawson]

Everything I see about installing Beta 1 is for a local machine.
I am setting up DSpace for my organization on a Ubuntu 18.04 remote server. 
I have DSPace 6 currently running but also wish to install and preview 
DSpace 7 Beta1 on another remote machine. The other machine is running 
Ubuntu 14.04 and has a working test install of Collection Space (which I 
don't need).

Do you have any suggestions or warnings regarding installing Beta 1 on a 
remote machine?
Is the installation procedure drastically different from a fresh install of 
DSpace 6?

-- 
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/ef13f0be-7195-4c53-813e-33d4420007b5%40googlegroups.com.