[dspace-tech] Re: What is VuFind and have you configured your DSpace 7.6 to import external metadata from it?
HI, Vufind is a Discovery software that adds a discovery interface on top of your other library software like dspace, or Koha, OJS, or any knowledge management software that you use in your library. The benefit it provides is, VuFind can provide a single-window search retrieval system for all your different library software. VuFind can connect to this software using OAI-PMH protocol to fetch and harvest metadata records and then index it locally in its solr search engine. Once that is done, You and your library users will be able to search and retrieve content from all your connected silos(Koha, Dspace, OJS). , at a single web interface, without going to individual software. Your search will also work, even if any of the connected software goes offline, in that case, Vufind will retrieve results from its local index. It is an amazing Open Source software if you want to implement a discovery system on top of your discrete knowledge management software. Regards Rupinder Singh On Wednesday 29 May, 2024 at 2:36:38 am UTC+5:30 Carolyn Sullivan wrote: > Hello all, > > I'm reviewing the options for importing external metadata to our DSpace > 7.6 instance to ensure we have all our API keys configured and etc. One of > the options for importing external metadata is through a resource called > VuFind. I googled it and found that it's apparently a discovery system. > Is this discovery system mostly available as an option for import to DSpace > for libraries running an instance of VuFind locally? Would a local > researcher be likely to use VuFind if my institution wasn't running VuFind > anyways? Trying to figure out (1) whether to configure it and (2) what id > I'd be using to pull in metadata if I DID configure it. > > Thanks, > Carolyn. > -- 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/80e43af4-c5e7-4bba-a4c0-12aaa44d2eaan%40googlegroups.com.
[dspace-tech] Dspace on Ubuntu 24.04
Hi, I just updated my dspace server to latest 24.04. and it made the installed tomcat 9 non functional.. when I checked the package was not there. When it tried reinstalling it with apt, it says "this release candidate is not available". So I installed whatever version was available on 24.04, which was Apache 10. Now my dspace server is not showing anything on 8080 REST interface, and web interface on port 4000 shows an error 500. What is the problem? Thanks Rupinder Singh -- 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/CAMLo0tUHEm6KCLc9iRKGsPO%2BakDz_Kvez0x-%3DweU6zwMinWT%3DQ%40mail.gmail.com.
[dspace-tech] Dspace 7.6 behind Apache Reverse Proxy
Hi,
I have been having this feeling that DSpace has been made unnecessarily
complicated by moving to this new angular UI. It is a pain to set up, and
then it's difficult to troubleshoot.
What I also don't understand Is why most of the documentation and most of
the support emails answer the questions thinking that everyone is running
DSpace locally. I mean, all of the demos, all of the instructions, mention
"localhost" or "127.0.0.1" everywhere.
Anyway.
I want to publish my repository over the web from an Apache server, but i
cant find a single post/wiki/article/support mail that can help in running
the DSpace angular UI behind the Apache Reverse proxy. So here is the
problem,
My server IP is 10.2.3.109 (This is translated to my Real IP in the
firewall and then to a domain)
the backend is running on 10.2.3.109:8080
the frontend is running on 10.2.3.109:4000
Everything works well, but I can't publish the repository on the web over
port 4000, so i decided to engage Apache Reverse proxy. With every needed
mod enabled and setting done, as follows
ServerName 10.2.3.109
#DSpace backend
ProxyPass /server http://10.2.3.109:8080/server
ProxyPassReverse /server http://10.2.3.109:8080/server
# angular UI
ProxyPass / http://10.2.3.109:4000/
ProxyPassReverse / http://10.2.3.109:4000/
With this, I can see my backend OAI page passed through Apache proxy with
the URL http://10.2.3.109/server. But whenever I open http://10.2.3.109 for
the angular UI, it flashes the Home page for a second and then gives Error
500. I can't figure out why this is happening; I also have
"rest.cors.allowed-origins = ${dspace.ui.url}" in my local.cfg file. But
that, too, is no help.
I have a running repository on Dspace 6.2, and I am doing this entire
exercise to upgrade and migrate to Dspace 7. But after bumping into all
this trouble, I am literally thinking of ditching Dspace and learning
something new like Invenio Framework, Fedora Commons, or maybe Greenstone.
Can anyone help, please?
Thank You
Rupinder Singh
--
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/4de30747-6691-4346-9749-231360bfe379n%40googlegroups.com.
[dspace-tech] Re: postfix installation
Hi, https://rupindersingh.in/postfix-configuration-for-koha-on-linux Please see if this helps, I wrote it while I configured postfix on my ubuntu server to work with koha... you just need to skip the koha configuration part, rest all would be same. On Sunday, March 19, 2023 at 6:12:40 PM UTC+5:30 Tom Obrien wrote: > Hi all, > I would like to setup Postfix mail server for dspace 6.3. The Dspace is > running on Ubuntu 22 but I have a chellenge is setting up mail server. Can > someone share a simple step by step instruction for installing and > configuring postfix to use gmail. > Regards > -- 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/38cb874b-7128-42cc-b183-8c524ec5d699n%40googlegroups.com.
[dspace-tech] Re: Dspace Data Migration with SAF
Dear Mr. AlMutairi, You were right, it was an issue with assetstore folder permissions and ownership. just one chown command and it was fixed. everything is now working as expected. But I still don't understand why AIP didn't work, and why it is so complicated. Anyway, I will continue to experiment with that. Thank you so much for all your help. That is all I needed, for now, to migrate my repository from the old server to a new one. We shall consider this case closed. Thank you once again. with regards Rupinder Singh Assistant Librarian Central University of Punjab On Wednesday, January 11, 2023 at 9:18:23 PM UTC+5:30 alo...@gmail.com wrote: > Maybe I should retire. :-) > [dspace]/bin/dspace index-discovery -b > > On Wednesday, January 11, 2023 at 6:44:58 PM UTC+3 Mohammad S. AlMutairi > wrote: > >> Hello Rupinder, >> >> You are almost there. You should have some clues in the log >> [dspace]/log/dspace.log ... This error ( An internal read or write >> operation failed ) suggest it could be a permission problem or the the >> assetstore is not where it expected to be (guessing) so check them both >> also make sure dc.identifier.uri links are correct for all the moved items >> and finally you need to do a discovery indexing [dspace]/bin/dspace >> discovery-index -b >> >> Good luck >> On Wednesday, January 11, 2023 at 3:31:47 PM UTC+3 jesse...@gmail.com >> wrote: >> >>> Dear Mr. AlMutairi, >>> That worked, and I was able to restore the database and the assetstore >>> on my new DSpace 7 installation. I can now see all the collections, >>> communities, and items on my Angular GUI. But as soon as i open any item, >>> It shows the metadata of the document uploaded but gives the following >>> error when is click the bitstream (a PDF dissertation in my case). >>> >>> Whitelabel Error Page >>> >>> This application has no explicit mapping for /error, so you are seeing >>> this as a fallback. >>> Wed Jan 11 17:56:55 IST 2023 >>> There was an unexpected error (type=Internal Server Error, status=500). >>> An internal read or write operation failed >>> >>> On Wednesday, January 11, 2023 at 10:43:58 AM UTC+5:30 Rupinder Singh >>> wrote: >>> >>>> Dear Mr. AlMutairi, >>>> I sent you copies of dspace.cfg, local.cfg, and bitstore.xml. on your >>>> personal mail. >>>> However, after your suggestion, I checked the local.cfg file and found >>>> that all the configuration settings were stored there and the assetstore >>>> folder is set to /mnt/dspace/assetstore . So I have taken a backup of it, >>>> and will now try restoring it on my DSPACE 7 test server as you suggested >>>> in your first mail. >>>> Please have a look at the config files though, we may come to find >>>> something more that went unnoticed before. >>>> >>>> Thank You >>>> Rupinder Singh >>>> >>>> On Tuesday, January 10, 2023 at 8:25:51 PM UTC+5:30 alo...@gmail.com >>>> wrote: >>>> >>>>> I wanted to warn you that bitstore.xml might have your >>>>> Amazon awsAccessKey, awsSecretKey, and bucketName so remove them if you >>>>> are >>>>> going to send the files or you can take it from here and move your >>>>> missing >>>>> assetstore to the server filesystem and follow the usual upgrade >>>>> procedure. >>>>> >>>>> On Tuesday, January 10, 2023 at 5:32:28 PM UTC+3 Mohammad S. AlMutairi >>>>> wrote: >>>>> >>>>>> Please forget AIP and SAF. >>>>>> >>>>>> Can you get me privately a copy of local.cfg, dspace.cfg and >>>>>> [dspace]/config/spring/api/bitstore.xml .. You can remove anything >>>>>> private >>>>>> data you think is worth removing ( database password, domain ..etc ). >>>>>> >>>>>> You need to read this: >>>>>> https://wiki.lyrasis.org/display/DSDOC6x/Storage+Layer#StorageLayer-ConfiguringtheBitstreamStore >>>>>> >>>>>> On Tuesday, January 10, 2023 at 5:09:15 PM UTC+3 jesse...@gmail.com >>>>>> wrote: >>>>>> >>>>>>> Thanks, Mr. ALMutairi, but no luck with that. >>>>>>> Surprisingly the old Dspace 6.2 server does not have any assetstore >>>>>>> folder, but the repository is working s
[dspace-tech] Re: Dspace Data Migration with SAF
Dear Mr. AlMutairi, That worked, and I was able to restore the database and the assetstore on my new DSpace 7 installation. I can now see all the collections, communities, and items on my Angular GUI. But as soon as i open any item, It shows the metadata of the document uploaded but gives the following error when is click the bitstream (a PDF dissertation in my case). Whitelabel Error Page This application has no explicit mapping for /error, so you are seeing this as a fallback. Wed Jan 11 17:56:55 IST 2023 There was an unexpected error (type=Internal Server Error, status=500). An internal read or write operation failed On Wednesday, January 11, 2023 at 10:43:58 AM UTC+5:30 Rupinder Singh wrote: > Dear Mr. AlMutairi, > I sent you copies of dspace.cfg, local.cfg, and bitstore.xml. on your > personal mail. > However, after your suggestion, I checked the local.cfg file and found > that all the configuration settings were stored there and the assetstore > folder is set to /mnt/dspace/assetstore . So I have taken a backup of it, > and will now try restoring it on my DSPACE 7 test server as you suggested > in your first mail. > Please have a look at the config files though, we may come to find > something more that went unnoticed before. > > Thank You > Rupinder Singh > > On Tuesday, January 10, 2023 at 8:25:51 PM UTC+5:30 alo...@gmail.com > wrote: > >> I wanted to warn you that bitstore.xml might have your >> Amazon awsAccessKey, awsSecretKey, and bucketName so remove them if you are >> going to send the files or you can take it from here and move your missing >> assetstore to the server filesystem and follow the usual upgrade procedure. >> >> On Tuesday, January 10, 2023 at 5:32:28 PM UTC+3 Mohammad S. AlMutairi >> wrote: >> >>> Please forget AIP and SAF. >>> >>> Can you get me privately a copy of local.cfg, dspace.cfg and >>> [dspace]/config/spring/api/bitstore.xml .. You can remove anything private >>> data you think is worth removing ( database password, domain ..etc ). >>> >>> You need to read this: >>> https://wiki.lyrasis.org/display/DSDOC6x/Storage+Layer#StorageLayer-ConfiguringtheBitstreamStore >>> >>> On Tuesday, January 10, 2023 at 5:09:15 PM UTC+3 jesse...@gmail.com >>> wrote: >>> >>>> Thanks, Mr. ALMutairi, but no luck with that. >>>> Surprisingly the old Dspace 6.2 server does not have any assetstore >>>> folder, but the repository is working somehow. I checked the assetstore >>>> location from the config file too, but, it's all on default, Searched for >>>> other installation locations, but found nothing. Actually, this server was >>>> installed long back by someone, who left the organization later. So this >>>> old DSpace server was left unattended for quite a long time. >>>> >>>> I created a test server with Dspace 6.2 with the same config, and tried >>>> restoring with AIP and SAF on it, Still got the same problems. AIP >>>> commands >>>> throws error >>>> java.lang.UnsupportedOperationException: Could not find a parent >>>> DSpaceObject referenced as '32116/180' in the METS Manifest for object >>>> hdl:32116/181. A parent DSpaceObject must be specified from either the >>>> 'packager' command or noted in the METS Manifest itself. >>>> >>>> and SAF import works only till it encounters an item that is part of >>>> another collection, then it gives an error saying >>>> Notice >>>> Import failed >>>> Attempted to create a handle which is already in use: 32116/2483 >>>> >>>> >>>> On Monday, January 9, 2023 at 6:25:01 PM UTC+5:30 alo...@gmail.com >>>> wrote: >>>> >>>>> Hello Rupinder, >>>>> >>>>> You really don't have to use SAF or AIP for this migration since you >>>>> own both systems ( old & new ). Both should work but It's time consuming >>>>> and sometimes flaky. There is a faster and a shorter path. Try it and let >>>>> us know in the list if you still need more help. I'll walk you through. >>>>> >>>>> 1) Dump the old database in a binary format ( pg_dump -Fc dspace > >>>>> dspace-6x.sql ) and copy it along with the old assetstore to the new >>>>> server. >>>>> 2) su - posgres >>>>> 3) Restore the database into the new server using ( pg_restore -v -c >>>>> -d dspace dspace-6x.sql ). You might need to run ( [dspac
[dspace-tech] Re: Dspace Data Migration with SAF
Dear Mr. AlMutairi, I sent you copies of dspace.cfg, local.cfg, and bitstore.xml. on your personal mail. However, after your suggestion, I checked the local.cfg file and found that all the configuration settings were stored there and the assetstore folder is set to /mnt/dspace/assetstore . So I have taken a backup of it, and will now try restoring it on my DSPACE 7 test server as you suggested in your first mail. Please have a look at the config files though, we may come to find something more that went unnoticed before. Thank You Rupinder Singh On Tuesday, January 10, 2023 at 8:25:51 PM UTC+5:30 alo...@gmail.com wrote: > I wanted to warn you that bitstore.xml might have your > Amazon awsAccessKey, awsSecretKey, and bucketName so remove them if you are > going to send the files or you can take it from here and move your missing > assetstore to the server filesystem and follow the usual upgrade procedure. > > On Tuesday, January 10, 2023 at 5:32:28 PM UTC+3 Mohammad S. AlMutairi > wrote: > >> Please forget AIP and SAF. >> >> Can you get me privately a copy of local.cfg, dspace.cfg and >> [dspace]/config/spring/api/bitstore.xml .. You can remove anything private >> data you think is worth removing ( database password, domain ..etc ). >> >> You need to read this: >> https://wiki.lyrasis.org/display/DSDOC6x/Storage+Layer#StorageLayer-ConfiguringtheBitstreamStore >> >> On Tuesday, January 10, 2023 at 5:09:15 PM UTC+3 jesse...@gmail.com >> wrote: >> >>> Thanks, Mr. ALMutairi, but no luck with that. >>> Surprisingly the old Dspace 6.2 server does not have any assetstore >>> folder, but the repository is working somehow. I checked the assetstore >>> location from the config file too, but, it's all on default, Searched for >>> other installation locations, but found nothing. Actually, this server was >>> installed long back by someone, who left the organization later. So this >>> old DSpace server was left unattended for quite a long time. >>> >>> I created a test server with Dspace 6.2 with the same config, and tried >>> restoring with AIP and SAF on it, Still got the same problems. AIP commands >>> throws error >>> java.lang.UnsupportedOperationException: Could not find a parent >>> DSpaceObject referenced as '32116/180' in the METS Manifest for object >>> hdl:32116/181. A parent DSpaceObject must be specified from either the >>> 'packager' command or noted in the METS Manifest itself. >>> >>> and SAF import works only till it encounters an item that is part of >>> another collection, then it gives an error saying >>> Notice >>> Import failed >>> Attempted to create a handle which is already in use: 32116/2483 >>> >>> >>> On Monday, January 9, 2023 at 6:25:01 PM UTC+5:30 alo...@gmail.com >>> wrote: >>> >>>> Hello Rupinder, >>>> >>>> You really don't have to use SAF or AIP for this migration since you >>>> own both systems ( old & new ). Both should work but It's time consuming >>>> and sometimes flaky. There is a faster and a shorter path. Try it and let >>>> us know in the list if you still need more help. I'll walk you through. >>>> >>>> 1) Dump the old database in a binary format ( pg_dump -Fc dspace > >>>> dspace-6x.sql ) and copy it along with the old assetstore to the new >>>> server. >>>> 2) su - posgres >>>> 3) Restore the database into the new server using ( pg_restore -v -c -d >>>> dspace dspace-6x.sql ). You might need to run ( [dspace]/bin/dspace >>>> database clean ) first and for this to work you need to add >>>> ( db.cleanDisabled=false ) at the top of ( [dspace]/config/dspace.cfg ) >>>> and >>>> no need to restart tomcat. >>>> 4) exit >>>> 5) Run [dspace]/bin/dspace database migrate ignored >>>> 6) Check [dspace]/bin/dspace status & info >>>> 7) [dspace]/bin/dspace create-administrator >>>> 8) Copy the old assetstore folder to where it should be in the new >>>> server [dspace]/assetstore >>>> 9) Chown -R tomcat:tomcat [dspace] >>>> 10) systemctl restart tomcat & finally check if everything is O.K. >>>> >>>> ** You can if you need to or have to dump the database in a text format >>>> and run search and replace on it for anything ( old domain and URL's that >>>> has xmlui in it comes in mind ). Do it after finishing step 3 above. >>>> a) su - postgres
[dspace-tech] Re: Dspace Data Migration with SAF
Thanks, Mr. ALMutairi, but no luck with that. Surprisingly the old Dspace 6.2 server does not have any assetstore folder, but the repository is working somehow. I checked the assetstore location from the config file too, but, it's all on default, Searched for other installation locations, but found nothing. Actually, this server was installed long back by someone, who left the organization later. So this old DSpace server was left unattended for quite a long time. I created a test server with Dspace 6.2 with the same config, and tried restoring with AIP and SAF on it, Still got the same problems. AIP commands throws error java.lang.UnsupportedOperationException: Could not find a parent DSpaceObject referenced as '32116/180' in the METS Manifest for object hdl:32116/181. A parent DSpaceObject must be specified from either the 'packager' command or noted in the METS Manifest itself. and SAF import works only till it encounters an item that is part of another collection, then it gives an error saying Notice Import failed Attempted to create a handle which is already in use: 32116/2483 On Monday, January 9, 2023 at 6:25:01 PM UTC+5:30 alo...@gmail.com wrote: > Hello Rupinder, > > You really don't have to use SAF or AIP for this migration since you own > both systems ( old & new ). Both should work but It's time consuming and > sometimes flaky. There is a faster and a shorter path. Try it and let us > know in the list if you still need more help. I'll walk you through. > > 1) Dump the old database in a binary format ( pg_dump -Fc dspace > > dspace-6x.sql ) and copy it along with the old assetstore to the new server. > 2) su - posgres > 3) Restore the database into the new server using ( pg_restore -v -c -d > dspace dspace-6x.sql ). You might need to run ( [dspace]/bin/dspace > database clean ) first and for this to work you need to add > ( db.cleanDisabled=false ) at the top of ( [dspace]/config/dspace.cfg ) and > no need to restart tomcat. > 4) exit > 5) Run [dspace]/bin/dspace database migrate ignored > 6) Check [dspace]/bin/dspace status & info > 7) [dspace]/bin/dspace create-administrator > 8) Copy the old assetstore folder to where it should be in the new server > [dspace]/assetstore > 9) Chown -R tomcat:tomcat [dspace] > 10) systemctl restart tomcat & finally check if everything is O.K. > > ** You can if you need to or have to dump the database in a text format > and run search and replace on it for anything ( old domain and URL's that > has xmlui in it comes in mind ). Do it after finishing step 3 above. > a) su - postgres > b) Dump the databse in text format ( pg_dump -c dspace > > dspace-migrated.sql ) > c) Search and replace using ( sed, awk, perl, vi or any text edit you feel > comfortable with ). > d) Restore it ( cat dspace.sql | psql -d dspace < dspace-migrated.sql ) > > Good luck > > > On Monday, January 9, 2023 at 7:11:11 AM UTC+3 jesse...@gmail.com wrote: > >> Can someone please help me with this? >> I am planning for migration and am stuck on this. AIP backup and restore >> are of no use because it throws too many errors. I found SAF to be simple >> and reliable, but the only problem is with these conflicts of items >> appearing in multiple collections. >> >> Please help >> >> Thank you >> Rupinder Singh >> On Tuesday, December 27, 2022 at 3:37:15 PM UTC+5:30 Rupinder Singh wrote: >> >>> I have a problem with SAF, as I am Migrating from Dspace 6.2 to DSpace >>> 7.4. I exported my collections from DSpace 6.2, But as I upload the SAF >>> items to my Dspace 7.4 everything goes ok, Except for the items which are >>> part of multiple collections. The import process exists with an error >>> saying that the Item/Handle Already Exists. >>> How can I resolve this conflict? There are many items that appear is >>> more than one collection in my existing Dspace 6.2. >>> >> -- 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/3a82b943-61c1-4312-ae0c-a2d3074e1c87n%40googlegroups.com.
[dspace-tech] Re: Dspace Data Migration with SAF
Can someone please help me with this? I am planning for migration and am stuck on this. AIP backup and restore are of no use because it throws too many errors. I found SAF to be simple and reliable, but the only problem is with these conflicts of items appearing in multiple collections. Please help Thank you Rupinder Singh On Tuesday, December 27, 2022 at 3:37:15 PM UTC+5:30 Rupinder Singh wrote: > I have a problem with SAF, as I am Migrating from Dspace 6.2 to DSpace > 7.4. I exported my collections from DSpace 6.2, But as I upload the SAF > items to my Dspace 7.4 everything goes ok, Except for the items which are > part of multiple collections. The import process exists with an error > saying that the Item/Handle Already Exists. > How can I resolve this conflict? There are many items that appear is more > than one collection in my existing Dspace 6.2. > -- 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/e660646e-dbec-4030-a77b-0a8ed62ab9a8n%40googlegroups.com.
[dspace-tech] Dspace Data Migration with SAF
I have a problem with SAF, as I am Migrating from Dspace 6.2 to DSpace 7.4. I exported my collections from DSpace 6.2, But as I upload the SAF items to my Dspace 7.4 everything goes ok, Except for the items which are part of multiple collections. The import process exists with an error saying that the Item/Handle Already Exists. How can I resolve this conflict? There are many items that appear is more than one collection in my existing Dspace 6.2. -- 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/d49a8210-e546-4122-91fd-d741aba6d461n%40googlegroups.com.
[dspace-tech] Re: File upload error on Dspace 7.4
Wonderful my friend. You are one great soul on earth. It worked like a charm. I was so desperate to see my installation working, and with this error, I was feeling helpless. Even the error logs didn't show any detail. But you gave the precise solution for my issue. Thank You so much. Rupinder Singh On Wednesday, November 30, 2022 at 5:49:11 PM UTC+5:30 alo...@gmail.com wrote: > Never mind: You need to find the tomcat systemd unit file > (tomcat9.service) if you install the default Ubuntu tomcat package and make > sure tomcat user you see in the unit file has write permission over the > DSpace folder and need to tell tomcat it can write into DSpace folder as > you see it highlted in red. > > [Service] > > # Configuration > Environment="CATALINA_HOME=/usr/share/tomcat9" > Environment="CATALINA_BASE=/var/lib/tomcat9" > Environment="CATALINA_TMPDIR=/tmp" > Environment="JAVA_OPTS=-Djava.awt.headless=true -Dfile.encoding=UTF-8" > > # Lifecycle > Type=simple > ExecStartPre=+/usr/libexec/tomcat9/tomcat-update-policy.sh > ExecStart=/bin/sh /usr/libexec/tomcat9/tomcat-start.sh > SuccessExitStatus=143 > Restart=on-abort > > # Logging > SyslogIdentifier=tomcat9 > > # Security > *User=tomcat* > Group=tomcat > PrivateTmp=yes > AmbientCapabilities=CAP_NET_BIND_SERVICE > NoNewPrivileges=true > CacheDirectory=tomcat9 > CacheDirectoryMode=750 > ProtectSystem=strict > ReadWritePaths=/etc/tomcat9/Catalina/ > ReadWritePaths=/var/lib/tomcat9/webapps/ > ReadWritePaths=/var/log/tomcat9/ > *ReadWritePaths=/opt/dspace* > > [Install] > WantedBy=multi-user.target > > On Wednesday, November 30, 2022 at 3:06:23 PM UTC+3 Mohammad S. AlMutairi > wrote: > >> Which Operating System are you using? >> >> On Wednesday, November 30, 2022 at 2:47:53 PM UTC+3 jesse...@gmail.com >> wrote: >> >>> Hi, >>> I am struggling to get this software to work for the last 2 months, and >>> still no success. >>> I did the Dspace 7.4 backend installation on my Ubuntu 22.04 computer, >>> installed Solr from source, installed tomcat9 from the apt package manager, >>> and compiled the DSpace code for the backend. >>> Everything is running under a dedicated 'DSpace' system user. It went >>> well and I can access the backend HAL interface on localhost:8080/server. >>> >>> Further, I went to install the frontend on the same machine, under the >>> same user (i.e., dspace), and installed node js, yarn, and everything as >>> mentioned in DSpace wiki, it also went well and I could see my DSpace 7 >>> home screen for the first time. It was beautiful and I was happy, I logged >>> in with my administrative users, and created some communities and >>> collections. it is all working. BUT I CAN NOT UPLOAD ANY FILE, NOT EVEN THE >>> COMMUNITY LOGO's. >>> I am so fed up with this software, Error logs are of no help. i thought >>> it would be a permission issue, but my system user 'dspace' is the owner of >>> both dspace backend folder, and also dspace-angular, tomcat9, Solr, and >>> yarn both are running under 'dsapce' system user. still, I can't upload >>> anything. I can't figure out what I did wrong, and where I'm missing >>> something, and at this point, I'm too tired to re-install it again and >>> again (like I've been doing for the last 2 months). >>> >>> Seriously!!, please help, I need to get this working. >>> >>> >>> Thank You >>> >>> Rupinder Singh >>> >>> -- 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/0aba2323-5690-431d-b300-ccb33cf3f15dn%40googlegroups.com.
[dspace-tech] File upload error on Dspace 7.4
Hi, I am struggling to get this software to work for the last 2 months, and still no success. I did the Dspace 7.4 backend installation on my Ubuntu 22.04 computer, installed Solr from source, installed tomcat9 from the apt package manager, and compiled the DSpace code for the backend. Everything is running under a dedicated 'DSpace' system user. It went well and I can access the backend HAL interface on localhost:8080/server. Further, I went to install the frontend on the same machine, under the same user (i.e., dspace), and installed node js, yarn, and everything as mentioned in DSpace wiki, it also went well and I could see my DSpace 7 home screen for the first time. It was beautiful and I was happy, I logged in with my administrative users, and created some communities and collections. it is all working. BUT I CAN NOT UPLOAD ANY FILE, NOT EVEN THE COMMUNITY LOGO's. I am so fed up with this software, Error logs are of no help. i thought it would be a permission issue, but my system user 'dspace' is the owner of both dspace backend folder, and also dspace-angular, tomcat9, Solr, and yarn both are running under 'dsapce' system user. still, I can't upload anything. I can't figure out what I did wrong, and where I'm missing something, and at this point, I'm too tired to re-install it again and again (like I've been doing for the last 2 months). Seriously!!, please help, I need to get this working. Thank You Rupinder Singh -- 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/CAMLo0tUVKbHYmeSpkatGhOk2fbitqZPwHGB1Ax%2B5HveHftMt%2BQ%40mail.gmail.com.
[dspace-tech] AIP Import error in Dspace 6.3
Hi, I have a production server where I'm running Dspace 6.3, that repository has handle number 32116, which is mentioned in the dspace.cfg file and also in the handle table of the databases. I was able to successfully export the entire site in AIP format. then i installed the same version of Dspace 6.3 but with latest dependencies, like latest PostgreSQL 14, latest java, and latest tomcat etc. it was installed successfully, the site is working, and i have created an administrator (l...@cup.edu.in) with the CLI as the initial configuration. rest other is blank. So when i try to import the entire site AIP backup, using the following command it gives an error. jesse@Library:/dspace/bin$ sudo ./dspace packager -s -a -f -t AIP -e > l...@cup.edu.in -p 32116/0 /home/jesse/Documents/KR@CUP > /AIP/allsite/entiresite.zip > > Destination parents: > > Owner: 32116/0 > Ingesting package located at /home/jesse/Documents/KR@CUP > /AIP/allsite/entiresite.zip > Also ingesting all referenced packages (recursive mode).. > This may take a while, please check your logs for ongoing status while we > process each package. > org.dspace.content.crosswalk.CrosswalkInternalException: > org.dspace.content.packager.PackageException: Group Administrator already > exists > at > org.dspace.content.crosswalk.RoleCrosswalk.ingest(RoleCrosswalk.java:344) > at > org.dspace.content.crosswalk.RoleCrosswalk.ingest(RoleCrosswalk.java:261) > at > org.dspace.content.packager.METSManifest.crosswalkXmd(METSManifest.java:1247) > at > org.dspace.content.packager.METSManifest.crosswalkObjectOtherAdminMD(METSManifest.java:1150) > at > org.dspace.content.packager.AbstractMETSIngester.ingestObject(AbstractMETSIngester.java:468) > at > org.dspace.content.packager.AbstractMETSIngester.ingest(AbstractMETSIngester.java:243) > at > org.dspace.content.packager.AbstractPackageIngester.ingestAll(AbstractPackageIngester.java:147) > at org.dspace.app.packager.Packager.ingest(Packager.java:517) > at org.dspace.app.packager.Packager.main(Packager.java:426) > 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) > Caused by: org.dspace.content.packager.PackageException: Group > Administrator already exists > at > org.dspace.content.packager.RoleIngester.ingestDocument(RoleIngester.java:297) > at org.dspace.content.packager.RoleIngester.ingest(RoleIngester.java:501) > at > org.dspace.content.crosswalk.RoleCrosswalk.ingest(RoleCrosswalk.java:340) > ... 14 more > org.dspace.content.crosswalk.CrosswalkInternalException: > org.dspace.content.packager.PackageException: Group Administrator already > exists > > upon checking the log i found that , it successfully read all the user information , and tried creating the e-people as well. but after that nothing appears, and this error shows on cli.. however i don't see any changes in the web UI (no groups, no e-people). I have also attached the copy of my mets.xml file from my allsite AIP zip folder. Where I'm doing wrong. I need to migrate my dspace from one server to another. please help me. Regards, Rupinder Singh Assistant Librarian Central University of Punjab | Bathinda -- 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/CAMLo0tX_qE1OsBJhTY5UHUOJjMjj2VhRmVcbrG_Ey11TS_e1hw%40mail.gmail.com. http://www.dspace.org/schema/aip/mets_aip_1_0.xsd; xmlns="http://www.loc.gov/METS/; xmlns:xlink="http://www.w3.org/1999/xlink; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/mets.xsd;> 321162018/0 DSpace 6.2 http://www.loc.gov/mods/v3; xmlns:xlink="http://www.w3.org/1999/xlink; xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd;>http://www.loc.gov/mods/v3; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd;> http://hdl.handle.net/321162018/0 http://kr.cup.edu.in
[dspace-tech] Question about Dspace 6.X
Hello all, I have this silly question but need to know; 1. is it mandatory to create a system user named 'dspace' ? if it's related to some permissions issue to /build or /dspace folder, why can't we grant permissions to the existing user and do our work with just that? I just cant understand this step. 2. I don't remember setting any particular password for postgres sql, because while running 'psql' commands, it asks for password for postgres user. and I don't have that. do I need to reset the default password to something of my choice, to perform backup /restore and other tasks on postgres CLI. (I'm asking because, MySQL has this kind of mechanism). 3. Does AIP backups, also restore the custom metadata fields, embargo settings, and other access restrictions? I need to move an existing site (running Dsapce 6.2 on old ubuntu 16.04 server) to a newer installation. or shall i just do it the old-fashioned way? (taking PostgresSQL backup along with assetstore) Please advise Thank You Rupinder Singh Assistant Librarian Central University of Punjab -- 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/CAMLo0tX6Ywfpg1QgjDkf09T3m5Tm36NcXQVymvvdeLGhEPuowA%40mail.gmail.com.
