[dspace-tech] DSpace 7 localization issue

[Andrew K]

Hello!

I noticed that the localization files lag behind. And this is perfectly 
normal.
The documentation says: "*When new keys are introduced, TODO messages are 
automatically added to the catalogs of other languages*" 
https://wiki.lyrasis.org/pages/viewpage.action?pageId=117735441#DSpace7TranslationInternationalization(i18n)Localization(l10n)-Translations(forexample,nl.json5)
But that does not happen, new keys are missing, at least for uk.json5. Is 
there a way to correct that?

And the next problem is that missing keys in the .json5 file are displayed 
as key names. It would be much much better if the English names were shown 
instead.
Is that possible?

Best regards,
Andrew

P.S.: 

-- 
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/c53a6149-c539-4506-8700-45a887272253n%40googlegroups.com.

[dspace-tech] Migration from 5.4 to 7.6

[Andrew K]

Hello!

I am trying to upgrade from 5.4 to the latest 7.6 version.
I installed the new server and copied the assetstore and database.
Then did 
sudo /dspace/bin/dspace database migrate ignored

sudo /dspace/bin/dspace database info

Database Type: postgres
Database URL: jdbc:postgresql://localhost:5432/dspace
Database Schema: public
Database Username: dspace
Database Software: PostgreSQL version 12.16 (Ubuntu 12.16-0ubuntu0.20.04.1)
Database Driver: PostgreSQL JDBC Driver version 42.6.0
PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)
FlywayDB Version: 8.4.4

+---++--+--+-+--+
| Category  | Version| Description 
 | Type | Installed On| State|
+---++--+--+-+--+
|   | 1  | << Flyway Baseline >>   
 | BASELINE | 2023-09-30 17:31:15 | Baseline |
| Versioned | 1.1| Initial DSpace 1.1 database schema   
| SQL  | 2023-09-30 17:31:15 | Success  |
| Versioned | 1.2| Upgrade to DSpace 1.2 schema 
| SQL  | 2023-09-30 17:31:15 | Success  |
| Versioned | 1.3| Upgrade to DSpace 1.3 schema 
| SQL  | 2023-09-30 17:31:15 | Success  |
| Versioned | 1.3.9  | Drop constraint for DSpace 1 4 schema   
 | JDBC | 2023-09-30 17:31:16 | Success  |
| Versioned | 1.4| Upgrade to DSpace 1.4 schema 
| SQL  | 2023-09-30 17:31:16 | Success  |
| Versioned | 1.5| Upgrade to DSpace 1.5 schema 
| SQL  | 2023-09-30 17:31:16 | Success  |
| Versioned | 1.5.9  | Drop constraint for DSpace 1 6 schema   
 | JDBC | 2023-09-30 17:31:16 | Success  |
| Versioned | 1.6| Upgrade to DSpace 1.6 schema 
| SQL  | 2023-09-30 17:31:16 | Success  |
| Versioned | 1.7| Upgrade to DSpace 1.7 schema 
| SQL  | 2023-09-30 17:31:16 | Success  |
| Versioned | 1.8| Upgrade to DSpace 1.8 schema 
| SQL  | 2023-09-30 17:31:16 | Success  |
| Versioned | 3.0| Upgrade to DSpace 3.x schema 
| SQL  | 2023-09-30 17:31:16 | Success  |
| Versioned | 4.0| Upgrade to DSpace 4.x schema 
| SQL  | 2023-09-30 17:31:16 | Success  |
| Versioned | 4.9.2015.10.26 | DS-2818 registry update 
 | SQL  | 2023-09-30 17:31:16 | Success  |
| Versioned | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy 
 | SQL  | 2023-09-30 17:31:16 | Success  |
| Versioned | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop 
constraint | JDBC | 2023-09-30 17:31:16 | Success  |
| Versioned | 5.0.2014.09.26 | DS-1582 Metadata For All Objects 
| SQL  | 2023-09-30 17:31:16 | Success  |
| Versioned | 5.0.2014.11.04 | Enable XMLWorkflow Migration 
| JDBC | 2023-09-30 17:31:16 | Success  |
| Versioned | 5.6.2016.08.23 | DS-3097 
 | SQL  | 2023-09-30 17:31:17 | Success  |
| Versioned | 5.7.2017.04.11 | DS-3563 Index metadatavalue resource type id 
column  | SQL  | 2023-09-30 17:31:17 | Success  |
| Versioned | 5.7.2017.05.05 | DS 3431 Add Policies for BasicWorkflow   
| JDBC | 2023-09-30 17:31:17 | Success  |
| Versioned | 6.0.2015.03.06 | DS 2701 Dso Uuid Migration   
| JDBC | 2023-09-30 17:31:17 | Success  |
| Versioned | 6.0.2015.03.07 | DS-2701 Hibernate migration 
 | SQL  | 2023-09-30 17:31:17 | Success  |
| Versioned | 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration 
| JDBC | 2023-09-30 17:31:18 | Success  |
| Versioned | 6.0.2015.09.01 | DS 2701 Enable XMLWorkflow Migration 
| JDBC | 2023-09-30 17:31:18 | Success  |
| Versioned | 6.0.2016.01.03 | DS-3024 
 | SQL  | 2023-09-30 17:31:18 | Success  |
| Versioned | 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables   
 | JDBC | 2023-09-30 17:31:18 | Success  |
| Versioned | 6.0.2016.02.25 | DS-3004-slow-searching-as-admin 
 | SQL  | 2023-09-30 

[dspace-tech] Re: Migration from 5.4 to 7.6

[Andrew K]

The error message also has this string

Caused by: java.nio.file.NoSuchFileException: 
/www/dspace/solr/statistics/data/index/segments_1

середа, 4 жовтня 2023 р. о 22:41:35 UTC+3 Andrew K пише:

Hello Tim, 

Thank you! I don't know how but the database was not imported. The problem 
solved.

Another problem: on the old server I run 
root@dspace:/www/dspace/bin # ./dspace *solr-export-statistics*
Exception: Expected mime type application/octet-stream but got text/html. 
Apache Tomcat/8.0.28 - Error 
reportH1 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
 
H2 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
 
H3 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
 
BODY 
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} 
P 
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
 
{color : black;}A.name {color : black;}.line {height: 1px; 
background-color: #525D76; border: none;} HTTP 
Status 500 - {msg=SolrCore 'statistics' is not available due to init 
failure: Error opening new 
searcher,trace=org.apache.solr.common.SolrException: SolrCore 'statistics' 
is not available due to init failure: Error opening new searcher

-- 
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/1ecb8adf-1a2e-4a23-bb14-2f8ba31cd5c0n%40googlegroups.com.

[dspace-tech] Re: Migration from 5.4 to 7.6

[Andrew K]

Hello Tim, 

Thank you! I don't know how but the database was not imported. The problem 
solved.

Another problem: on the old server I run 
root@dspace:/www/dspace/bin # ./dspace *solr-export-statistics*
Exception: Expected mime type application/octet-stream but got text/html. 
Apache Tomcat/8.0.28 - Error 
reportH1 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
 
H2 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
 
H3 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
 
BODY 
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} 
P 
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
 
{color : black;}A.name {color : black;}.line {height: 1px; 
background-color: #525D76; border: none;} HTTP 
Status 500 - {msg=SolrCore 'statistics' is not available due to init 
failure: Error opening new 
searcher,trace=org.apache.solr.common.SolrException: SolrCore 'statistics' 
is not available due to init failure: Error opening new searcher
at 
org.apache.solr.core.CoreContainer.getCore(CoreContainer.java:745)
at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:299)
at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.dspace.solr.filters.LocalHostRestrictionFilter.doFilter(LocalHostRestrictionFilter.java:50)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
and so on, very long error message.

The old server is running.
What is the problem, how can I move the solr data to the new server?

середа, 4 жовтня 2023 р. о 19:42:10 UTC+3 DSpace Technical Support пише:

> Hi Andrew,
>
> Based on the information you shared, it appears (to me) that you ran the 
> "dspace database migrate ignored" command on an **empty** database.  If you 
> look, the "info" command reported that the "Installed On" date for every 
> single migration was Sept 30, 2023.  That implies that the database had no 
> prior content or database tables.
>
> I suspect you may have forgotten to migrate your database over from 5.x to 
> 7.x?  If it's helpful, we have a migration guide which can walk through 
> those steps here: 
> https://wiki.lyrasis.org/display/DSDOC7x/Migrating+DSpace+to+a+new+server
>
> It is also possible to simply follow the Upgrading guide, but it tends to 
> "assume" your database data is already in place: 
> https://wiki.lyrasis.org/display/DSDOC7x/Upgrading+DSpace
>
> Tim
>
> On Saturday, September 30, 2023 at 10:03:24 AM UTC-5 Andrew K wrote:
>
>> Hello!
>>
>> I am trying to upgrade from 5.4 to the latest 7.6 version.
>> I installed the new server and copied the assetstore and database.
>> Then did 
>> sudo /dspace/bin/dspace database migrate ignored
>>
>> sudo /dspace/bin/dspace database info
>>
>> Database Type: postgres
>> Database URL: jdbc:postgresql://localhost:5432/dspace
>> Database Schema: public
>> Database Username: dspace
>> Database Software: PostgreSQL version 12.16 (Ubuntu 
>> 12.16-0ubuntu0.20.04.1)
>> Database Driver: PostgreSQL JDBC Driver version 42.6.0
>> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)
>> FlywayDB Version: 8.4.4
>>
>>
>> +---++--+--+-+--+
>> | Category  | Version| Description   
>>| Type | Installed On| State|
>>
>> +---++--+--+-+--+
>> |   | 1  | << Flyway Baseline >> 
>>| BASELINE | 2023-09-30 17:31:15 | Baseline |
>> | Versioned | 1.1| Initial DSpace 1.1 database schema 
>>   | SQL  | 2023-09-30 17:31:15 | Success  |
>> | Versioned | 1.2| Upgrade to DSpace 1.2 schema   
>>   | SQL  | 2023-09-30 17:31:15 | Success  |
>> | Versioned | 1.3| Upgrade to DSpace 1.3 schema   
>>   | SQL  | 2023-09-30 17:31:15 | Success  |
>&

[dspace-tech] Re: Migration from 5.4 to 7.6

[Andrew K]

Thank you, Tim!

It looks like solr is not installed on that server. And it has been online 
for 7 years like this. Pity.

Another question.
I moved the database and assetstore to the new server.
Then I did 
*sudo /dspace/bin/dspace filter-media*
It took more than a day to complete (12+K items).
Now I try 
*sudo /dspace/bin/dspace index-discovery*
but it fails:




*The script has startedUpdating Indexjava.lang.IllegalArgumentException: 
More than one result foundat 
org.dspace.core.AbstractHibernateDAO.uniqueResult(AbstractHibernateDAO.java:242)
  
  at 
org.dspace.content.dao.impl.WorkspaceItemDAOImpl.findByItem(WorkspaceItemDAOImpl.java:81)*

What is going on, please?

Also, when I imported the database, there was an error in the end
...




*ALTER TABLE REVOKE psql:db.sql:603904: ERROR: role "pgsql" does not exist 
psql:db.sql:603905: ERROR: role "pgsql" does not exist GRANT*

There was *psql* role and user instead of *postgres *on the old server.
Is that a problem I should correct somehow?

Thanks,
Andrew

середа, 4 жовтня 2023 р. о 23:08:42 UTC+3 DSpace Technical Support пише:

> Hi Andrew,
>
> As that "Caused by" error notes, it appears that Solr cannot find your 
> statistics data in the "/www/dspace/solr/statistics/data/" folder (and the 
> subfolders under that).
>
> Are you certain you have statistics data in that specific location on your 
> filesystem?   Are you sure that Solr is up and running while you try to do 
> the export?
>
> You also might want to check Solr's own logs, as it's possible more 
> detailed information is available there.  It could be a simple permissions 
> issue, or a configuration issue, or any number of other things.
>
> Good luck,
>
> Tim
>
> On Wednesday, October 4, 2023 at 2:43:58 PM UTC-5 Andrew K wrote:
>
>> The error message also has this string
>>
>> Caused by: java.nio.file.NoSuchFileException: 
>> /www/dspace/solr/statistics/data/index/segments_1
>>
>> середа, 4 жовтня 2023 р. о 22:41:35 UTC+3 Andrew K пише:
>>
>> Hello Tim, 
>>
>> Thank you! I don't know how but the database was not imported. The 
>> problem solved.
>>
>> Another problem: on the old server I run 
>> root@dspace:/www/dspace/bin # ./dspace *solr-export-statistics*
>> Exception: Expected mime type application/octet-stream but got text/html. 
>> Apache Tomcat/8.0.28 - Error 
>> reportH1 
>> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
>>  
>> H2 
>> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
>>  
>> H3 
>> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
>>  
>> BODY 
>> {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B 
>> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} 
>> P 
>> {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
>>  
>> {color : black;}A.name {color : black;}.line {height: 1px; 
>> background-color: #525D76; border: none;} HTTP 
>> Status 500 - {msg=SolrCore 'statistics' is not available due to init 
>> failure: Error opening new 
>> searcher,trace=org.apache.solr.common.SolrException: SolrCore 'statistics' 
>> is not available due to init failure: Error opening new searcher
>>
>>

-- 
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/0e26af2b-b8aa-4424-a783-31d816586585n%40googlegroups.com.

[dspace-tech] Re: Migration from 5.4 to 7.6

[Andrew K]

I probably should have mentioned that I run 
*sudo /dspace/bin/dspace index-discovery -b*
on the new server first and it went OK.
After that I did 
*sudo /dspace/bin/dspace filter-media*
and then 
*sudo /dspace/bin/dspace index-discovery*
throws the error *java.lang.IllegalArgumentException: More than one result 
found*

Another question.
I moved the database and assetstore to the new server.
Then I did 
*sudo /dspace/bin/dspace filter-media*
It took more than a day to complete (12+K items).
Now I try 
*sudo /dspace/bin/dspace index-discovery*
but it fails:




*The script has startedUpdating Indexjava.lang.IllegalArgumentException: 
More than one result foundat 
org.dspace.core.AbstractHibernateDAO.uniqueResult(AbstractHibernateDAO.java:242)
  
  at 
org.dspace.content.dao.impl.WorkspaceItemDAOImpl.findByItem(WorkspaceItemDAOImpl.java:81)*

-- 
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/7dfd518f-5a28-431e-8b77-b2075405c913n%40googlegroups.com.

[dspace-tech] Re: Migration from 5.4 to 7.6

[Andrew K]

Hello Tim,

Thank you! It did the job perfectly. I found and deleted 3 duplicate items.

Another question now.
All the imported items have URI 
http://oldserver/jspui/handle/123456789/12345
But I need them https://newserver/handle/123456789/12345
What is the best way to replace all at once?

Thanks,
Andrew

понеділок, 16 жовтня 2023 р. о 23:13:11 UTC+3 DSpace Technical Support пише:

> Hi Andrew,
>
> Apologies for not getting back to this. I'm not always able to answer 
> questions on this list quickly, but I see no one else has gotten to this 
> one.
>
> The "More than one result found" error appears to be saying that somehow 
> you have *two* WorkspaceItem objects that link to the same Item.  In other 
> words, somehow you have two entries in the "workspaceitem" table which have 
> the *same value* in the "item_id" column.  That's not supposed to be 
> possible in DSpace, as every workspace Item should be linked to a different 
> Item.
>
> You should be able to find the duplicate entry by running something like 
> this:
>
>  select item_id, COUNT(item_id) from workspaceitem group by item_id having 
> count(item_id)>1;
>
> That should return duplicate "item_id" values.  Then, for each, you'd have 
> to find the duplicate rows:
> select * from workspaceitem where item_id=[value];
>
> It's unclear to me why you have duplicates, but there should not be two 
> rows with the same "item_id".  So, you should delete one of them.
>
> It's difficult to answer your other question about the "psql" role.  It 
> might be possible to ignore if that role is no longer necessary in your new 
> setup.  But, if you notice odd permissions errors, then it's possible that 
> role is needed.
>
> Tim
> On Friday, October 6, 2023 at 3:02:06 PM UTC-5 Andrew K wrote:
>
>> I probably should have mentioned that I run 
>> *sudo /dspace/bin/dspace index-discovery -b*
>> on the new server first and it went OK.
>> After that I did 
>> *sudo /dspace/bin/dspace filter-media*
>> and then 
>> *sudo /dspace/bin/dspace index-discovery*
>> throws the error *java.lang.IllegalArgumentException: More than one 
>> result found*
>>
>> Another question.
>> I moved the database and assetstore to the new server.
>> Then I did 
>> *sudo /dspace/bin/dspace filter-media*
>> It took more than a day to complete (12+K items).
>> Now I try 
>> *sudo /dspace/bin/dspace index-discovery*
>> but it fails:
>>
>>
>>
>>
>> *The script has startedUpdating Indexjava.lang.IllegalArgumentException: 
>> More than one result foundat 
>> org.dspace.core.AbstractHibernateDAO.uniqueResult(AbstractHibernateDAO.java:242)
>>   
>>   at 
>> org.dspace.content.dao.impl.WorkspaceItemDAOImpl.findByItem(WorkspaceItemDAOImpl.java:81)*
>>
>>

-- 
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/f40e822b-7406-4947-bc09-38b0fa44c8abn%40googlegroups.com.

[dspace-tech] Re: Enhancing Search for Google scholar on DSpace 7.4

[Andrew K]

Hey   Lewatle,

1. Did you have this problem with Google Scholar indexing on a 
previous DSpace versions?

2. What exactly have you done? *google-metadata.enable* = *true  *is 
default in DSpace 7.

Thanks
Andrew

четвер, 23 березня 2023 р. о 10:44:09 UTC+2 Lewatle Johannes Phaladi пише:

> Dear DSpace Tech Colleagues,
>
> This is confirmation that items from our DSpace site are now found on 
> Google Scholar.
>
> Regards,
> Lewatle 
>
> On Tuesday, 14 March 2023 at 13:10:15 UTC+2 Lewatle Johannes Phaladi wrote:
>
>> Dear DSpace Colleagues,
>>
>> On DSpace 7.4 when searching items by titles I am able to find few from 
>> Google Scholar https://scholar.google.com, others are not searchable, is 
>> there anyway to make Google Scholar to index our site for items to be 
>> visible, please see this links that I have followed:
>>
>> https://wiki.lyrasis.org/display/DSDOC6x/Google+Scholar+Metadata+Mappings
>> https://wiki.lyrasis.org/display/DSDOC6x/Search+Engine+Optimization
>>
>> Regards,
>> Lewatle 
>>
>>
>>

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

[dspace-tech] index-discovery error

[Andrew K]

Hello!

I have a 7.5 server updated from 5.4.
The database update process finished OK.
But the index-discovery fails. 

2023-03-20 09:24:03.611 INFO index-discovery - 4 @ The script has started 
2023-03-20 09:24:03.611 INFO index-discovery - 4 @ Updating Index 
2023-03-20 09:24:43.049 ERROR index-discovery - 4 @ null 2023-03-20 
09:24:43.050 ERROR index-discovery - 4 @ 
java.lang.IllegalArgumentException: More than one result found at 
org.dspace.core.AbstractHibernateDAO.uniqueResult(AbstractHibernateDAO.java:242)
 
at 
org.dspace.content.dao.impl.WorkspaceItemDAOImpl.findByItem(WorkspaceItemDAOImpl.java:81)
 
at 
org.dspace.content.WorkspaceItemServiceImpl.findByItem(WorkspaceItemServiceImpl.java:243)
 
at 
org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:1408) 
at 
org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:92) 
at 
org.dspace.discovery.SolrServiceResourceRestrictionPlugin.additionalIndex(SolrServiceResourceRestrictionPlugin.java:129)
 
at 
org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:67)
 
at 
org.dspace.discovery.indexobject.InprogressSubmissionIndexFactoryImpl.buildDocument(InprogressSubmissionIndexFactoryImpl.java:51)
 
at 
org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:63)
 
at 
org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:30)
 
at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:169) at 
org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:159) 
at 
org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:344) 
at 
org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:331) 
at org.dspace.discovery.IndexClient.internalRun(IndexClient.java:130) at 
org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:104) at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 
at java.base/java.lang.Thread.run(Thread.java:829)The database info
Database Type: postgres
Database URL: jdbc:postgresql://localhost:5432/dspace
Database Schema: public
Database Username: dspace
Database Software: PostgreSQL version 14.7 (Ubuntu 14.7-0ubuntu0.22.04.1)
Database Driver: PostgreSQL JDBC Driver version 42.4.3
PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)
FlywayDB Version: 8.4.4

+---++--+--+-+--+
| Category  | Version| Description 
 | Type | Installed On| State|
+---++--+--+-+--+
|   | 1  | << Flyway Init >>   
 | BASELINE | 2016-02-15 00:03:53 | Baseline |
| Versioned | 1.1| Initial DSpace 1.1 database schema   
| SQL  | 2016-02-15 00:03:53 | Success  |
| Versioned | 1.2| Upgrade to DSpace 1.2 schema 
| SQL  | 2016-02-15 00:03:54 | Success  |
| Versioned | 1.3| Upgrade to DSpace 1.3 schema 
| SQL  | 2016-02-15 00:03:54 | Success  |
| Versioned | 1.3.9  | Drop constraint for DSpace 1 4 schema   
 | JDBC | 2016-02-15 00:03:54 | Success  |
| Versioned | 1.4| Upgrade to DSpace 1.4 schema 
| SQL  | 2016-02-15 00:03:54 | Success  |
| Versioned | 1.5| Upgrade to DSpace 1.5 schema 
| SQL  | 2016-02-15 00:03:54 | Success  |
| Versioned | 1.5.9  | Drop constraint for DSpace 1 6 schema   
 | JDBC | 2016-02-15 00:03:54 | Success  |
| Versioned | 1.6| Upgrade to DSpace 1.6 schema 
| SQL  | 2016-02-15 00:03:54 | Success  |
| Versioned | 1.7| Upgrade to DSpace 1.7 schema 
| SQL  | 2016-02-15 00:03:54 | Success  |
| Versioned | 1.8| Upgrade to DSpace 1.8 schema 
| SQL  | 2016-02-15 00:03:54 | Success  |
| Versioned | 3.0| Upgrade to DSpace 3.x schema 
| SQL  | 2016-02-15 00:03:54 | Success  |
| Versioned | 4.0| Upgrade to DSpace 4.x schema 
| SQL  | 2016-02-15 00:03:54 | Success  |
| Versioned | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy 
 | 

[dspace-tech] Item URL in DSpace 7.5

[Andrew K]

Hello!

I just updated our DSpace 5.4 to 7.5 following the wiki.
In the new version item URL in browser looks like 
*website/items/e3fa1110-74f4-4f02-87d6-39f60763fe11*
While in the old version we had *website/jspui/handle/123456789/12345*

Is there any way to switch back to handle-type URLs?

Thanks,
Andrew

-- 
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/2c4e638d-f88b-4427-a3c2-ba7b25354f8an%40googlegroups.com.

[dspace-tech] Disk partitioning for DSpace 7

[Andrew K]

Hi everybody!

What is the optimum disk partitioning for DSpace 7?

I use a VDS, so the space is important. The aim is to have the system 
partition 20-30GB and keep everything else on another partition, including 
logs (they are very important AFAIK)..

What is the best way to organize everything?

Thanks,
Andrew

-- 
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/977c2dfa-d585-49a0-8284-f88401dfae76n%40googlegroups.com.

Re: [dspace-tech] Re: index-discovery error

[Andrew K]

Hi Tim,

Thanks a lot for your reply!

I exported the table *workspaceitem* and found no identical "item_id"
numbers. Since I do not care about those old (partially) submitted items, I
wanted to delete everything in the admin/workflow zone on the website, but
somehow it's not possible for those old submissions.
So I just truncated the *workspaceitem* table in the database. And it
worked! Now index-discovery goes smoothly. Yay!

Can I also ask you if it's possible to keep the old handle-type URLs in
DSpace 7 ?

Best regards,
Andrew

вт, 21 бер. 2023 р. о 18:34 'Tim Donohue' via DSpace Technical Support <
dspace-tech@googlegroups.com> пише:

>
> Hi,
>
> Based on that error message, it sounds like you somehow have invalid data
> in your "workspaceitem" database table (this table is used to store
> information about in-progress submissions).  The error seems to be saying
> that you have two different entries in the "workspaceitem" table which
> reference the *same* "item_id".  That shouldn't be possible, as each
> WorkspaceItem should have a *unique* "item_id".
>
> I'm not sure how that could have occurred. But if you can find the
> duplicate entry in "workspaceitem", then it should be possible to just
> remove one of the entries.  I'd recommend making a copy of the database
> before doing this, as it's possible there could be side effects that I'm
> not foreseeing.  Once that duplicate entry is removed though, I suspect the
> indexing will work properly.
>
> Tim
> On Monday, March 20, 2023 at 2:30:32 AM UTC-5 Andrew K wrote:
>
>> Hello!
>>
>> I have a 7.5 server updated from 5.4.
>> The database update process finished OK.
>> But the index-discovery fails.
>>
>> 2023-03-20 09:24:03.611 INFO index-discovery - 4 @ The script has started
>> 2023-03-20 09:24:03.611 INFO index-discovery - 4 @ Updating Index
>> 2023-03-20 09:24:43.049 ERROR index-discovery - 4 @ null 2023-03-20
>> 09:24:43.050 ERROR index-discovery - 4 @
>> java.lang.IllegalArgumentException: More than one result found at
>> org.dspace.core.AbstractHibernateDAO.uniqueResult(AbstractHibernateDAO.java:242)
>> at
>> org.dspace.content.dao.impl.WorkspaceItemDAOImpl.findByItem(WorkspaceItemDAOImpl.java:81)
>> at
>> org.dspace.content.WorkspaceItemServiceImpl.findByItem(WorkspaceItemServiceImpl.java:243)
>> at
>> org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:1408)
>> at
>> org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:92)
>> at
>> org.dspace.discovery.SolrServiceResourceRestrictionPlugin.additionalIndex(SolrServiceResourceRestrictionPlugin.java:129)
>> at
>> org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:67)
>> at
>> org.dspace.discovery.indexobject.InprogressSubmissionIndexFactoryImpl.buildDocument(InprogressSubmissionIndexFactoryImpl.java:51)
>> at
>> org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:63)
>> at
>> org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:30)
>> at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:169) at
>> org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:159)
>> at
>> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:344)
>> at
>> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:331)
>> at org.dspace.discovery.IndexClient.internalRun(IndexClient.java:130) at
>> org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:104) at
>> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>> at
>> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>> at java.base/java.lang.Thread.run(Thread.java:829)The database info
>> Database Type: postgres
>> Database URL: jdbc:postgresql://localhost:5432/dspace
>> Database Schema: public
>> Database Username: dspace
>> Database Software: PostgreSQL version 14.7 (Ubuntu 14.7-0ubuntu0.22.04.1)
>> Database Driver: PostgreSQL JDBC Driver version 42.4.3
>> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)
>> FlywayDB Version: 8.4.4
>>
>>
>> +---++--+--+-+--+
>> | Category  | Version| Description
>>| Type | Installed On| State|
>>
>> +---++-

Re: [dspace-tech] Disk partitioning for DSpace 7

[Andrew K]

Hello Mark,

Thanks a lot for the comprehensive reply and valuable insights. I will try 
to implement. Might need to start over with the server, though. Or wait and 
see how it goes first.

Best regards,
Andrew

середа, 12 квітня 2023 р. о 15:38:42 UTC+3 Mark H. Wood пише:

On Tue, Apr 11, 2023 at 08:56:07AM -0700, Andrew K wrote: 
> What is the optimum disk partitioning for DSpace 7? 

"Optimum" will be strongly dependent on (a) your OS and (b) how much 
you are storing in your repository. 

> I use a VDS, so the space is important. The aim is to have the system 
> partition 20-30GB and keep everything else on another partition, 
including 
> logs (they are very important AFAIK).. 

That seems sensible. 

I don't think anyone is going to have a "best way" for you, but here's 
what I've done. 

o I like to keep the Solr cores and the database each on its own 
volume. That way /var can fill up with log files and not stop 
DSpace. (These days, the DBMS is on a separate host, and I'd like 
to move Solr to yet another since they tend to become busy at the 
same time.) 

o I invented a configuration parameter 'dspace.var' and use it 
throughout the configuration, wherever DSpace is configured to 
store volatile files such as exported materials and the assetstore. 
Code and configuration are installed on the /opt volume and the 
rest is mounted on /var/lib/dspace. This last is again a separate 
volume. 

I've installed Monit to keep Tomcat, Solr and PostgreSQL running, 
monitor availability, restart anything that gets wedged, and email me 
if there's anything it can't handle. I also have the critical storage 
volumes monitored in case one comes close to filling up. 

I strongly recommend using a logical volume layer on top of a very 
simple physical partitioning scheme, so that you can add physical 
volumes online and portion them out as needed when logical volumes 
fill up. Usually I'll set up physical partitions "/" and "/boot", and 
make all the rest a single LVM PV partition, leaving some uncommitted 
storage in case I need to expand an LV more quickly than our corporate 
virtual-machine infrastructure can respond to my request. If I need 
to add physical storage, I can join it to the existing volume group, 
add slices to LVs as needed, and expand the LVs' filesystems into the 
new extents, all without interrupting service. (You don't need to 
understand *all* of that on Day 1, but getting the basics done at 
installation will make life so much nicer as the repository grows.) 

I need to say that usually on a new host I'll take a wild guess about 
how much storage will be needed for each of these various functions, 
then adjust when I see how the system is really operating. Some of my 
guesses have been quite over-generous. It's much harder to shrink a 
volume than to expand one, even on LVM. These days I'd probably 
request just as much physical storage, but leave more of it 
uncommitted and watch growth more closely. 

In the end, only a running system can tell you *precisely* what it 
needs to function adequately and reliably. Provide yourself with good 
system management tools and the ability to readily add capacity if you 
need it. Always give your systems a thorough inspection for capacity 
as annual budget time approaches. 

-- 
Mark H. Wood 
Lead Technology Analyst 

University Library 
Indiana University - Purdue University Indianapolis 
755 W. Michigan Street 
Indianapolis, IN 46202 
317-274-0749 
www.ulib.iupui.edu 

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

[dspace-tech] Intermittent 500 error

[Andrew K]

Hello,

I have a working 7.6 production server.
But sometimes (pretty often recently) there's a 500 Service Unavailable 
error.
I check the /server url, it seems to work OK.
I restart solr, pm2, tomcat - still this error. I reboot the server - the 
error is gone.

If I middle click to the top left logo and open a few instances in new tabs 
- some of them load OK, some of them have 500 error.

The server load is very low, like 0.5.

I looked to the browser console. There are some errors, attached.
Please help eliminate this problem!

Thanks,
Andrew

[image: 2024-02-10_163348.png][image: 2024-02-10_163446.png]

-- 
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/b3a42964-c42d-4d00-ac0c-94d028f441a3n%40googlegroups.com.

[dspace-tech] Re: Intermittent 500 error

[Andrew K]

I forgot to mention that nothing pops out in the logs.

-- 
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/955b6192-74e6-4a8b-91df-70e95433fd13n%40googlegroups.com.

[dspace-tech] SOLR error importing statistics

[Andrew K]

Hello!

I am trying to import statistics from 7.6 to 7.6.1 server and getting this 
error

# /dspace/bin/dspace solr-import-statistics
No index name provided, defaulting to "statistics".
Exception: Error from server at http://localhost:8983/solr/statistics: 
Server error writing document id 4c6a127a-31e0-46c3-9a11-21c289848623 to 
the index
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
from server at http://localhost:8983/solr/statistics: Server error writing 
document id 4c6a127a-31e0-46c3-9a11-21c289848623 to the index
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:681)
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:266)
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:248)
at 
org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1290)
at 
org.dspace.util.SolrImportExport.importIndex(SolrImportExport.java:465)
at org.dspace.util.SolrImportExport.main(SolrImportExport.java:148)
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:283)
at 
org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:134)
at 
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:99)

There's a similar thread 
https://groups.google.com/u/2/g/dspace-tech/c/GshVU2RXE8w/m/FTUL2eCWBQAJ
But in my case it says nothing about very long strings, just error

Any help would be appreciated.
Thank you!

WBR, 
Andrew

-- 
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/e05578e8-22ea-4f0e-9e8d-01848cbc4a81n%40googlegroups.com.

[dspace-tech] Re: REST port 80

[Andrew K]

Hi Steve,

Here's the manual I followed to switch to SSL
https://repozitar.fhv.uniza.sk/items/5b8d7e58-8e9c-4280-85d3-9d7c4b49b4d7

I also noticed that you have nameSpace: /xmlui in the config files. I think 
it should be nameSpace: /

Best regards,
Andrew
понеділок, 18 грудня 2023 р. о 23:57:02 UTC+2 Steve Michaels пише:

> I've been having difficulty getting my instance of 7.6 to run on SSL.
>
> One of the things I've noticed is that the config.json file has the REST 
> interface running SSL on port 80:
> {
>   "production": true,
>   "debug": true,
>   "ui": {
> "ssl": false,
> "host": "localhost",
> "port": 4000,
> "nameSpace": "/xmlui",
> "rateLimiter": {
>   "windowMs": 6,
>   "max": 500
> },
> "useProxies": true,
> "baseUrl": "http://localhost:4000/xmlui;
>   },
>   "rest": {
> "ssl": true,
> "host": "10.101.150.11",
> "port": 80,
> "nameSpace": "/server",
> "baseUrl": "https://10.101.150.11/server;
>   },
> [--SNIP--]
> when the config.*.yml clearly has:
> ui:
>   ssl: false
>   host: localhost
>   port: 4000
>   nameSpace: /xmlui
> #  baseUrl": http://localhost:4000
> rest:
>   ssl: true
>   host: 10.101.150.11
>   port: 443
>   nameSpace: /server
> #baseUrl: https://10.101.150.11/server
>
> Does this make a difference and why is the compiled config.json file wrong?
>

-- 
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/71115b27-7eb5-4c2f-964d-2fa48c93ac15n%40googlegroups.com.

[dspace-tech] Re: Connection Issues on Local Network

[Andrew K]

Hello Sidney,

A local DNS server can easily solve the problem.

середу, 20 грудня 2023 р. о 13:32:18 UTC+2 Sidney Campos пише:

> *Good morning!*
>
> *I continue on my mission to make DSpace work perfectly on my Windows 10 
> server* 
>
> With the current settings, I can access DSpace on the server via 
> https://fevasf-repositorio.ddns.net. I can also access it from outside 
> the local network. However, I am unable to access it from other computers 
> on the local network, under the same gateway as the server.
>
> I can only access it on the local network when I add the entry 
> 192.168.100.199 fevasf-repositorio.ddns.net to the hosts files on the 
> computers in the LAN. This is not a suitable solution as students will be 
> accessing it via WiFi using the same network as the computer and won't be 
> able to connect.
>
> I can access using :4000 on local network machines, but it 
> redirects to error 500 after some seconds.
>
> I am using DSpace 7 with Nginx, Tomcat, and Windows 10. 
>
> *My Nginx configuration is as follows:*
>
> server {
> listen 80;
> server_name fevasf-repositorio.ddns.net;
> rewrite ^ https://fevasf-repositorio.ddns.net permanent;
> }
>
> server {
> listen 443 ssl;
> server_name fevasf-repositorio.ddns.net;
>
> root "C:/Program Files/Apache Software Foundation/Tomcat 9.0/webapps";
>
> ssl_certificate C:/nginx-1.25.3/certs/fullchain.pem;
> ssl_certificate_key C:/nginx-1.25.3/certs/privkey.pem;
>
> location /server {
> proxy_set_header X-Forwarded-Proto https;
> proxy_set_header X-Forwarded-Host $host;
> proxy_pass http://localhost:8080/server;
> }
>
> location / {
> proxy_set_header X-Forwarded-Proto https;
> proxy_set_header X-Forwarded-Host $host;
> proxy_pass http://localhost:4000;
> }
> }
>
> *My Windows hosts file contains:*
>
> 192.168.100.199 fevasf-repositorio.ddns.net
>
> *My DSpace configuration is:* 
>
> ui:
>   ssl: false
>   host: fevasf-repositorio.ddns.net
>   port: 4000
>   nameSpace: /
>
>   rateLimiter:
> windowMs: 6 # 1 minute
> max: 500 # limit each IP to 500 requests per windowMs
>   useProxies: true
>
> rest:
>   ssl: true
>   host: fevasf-repositorio.ddns.net
>   port: 443
>   nameSpace: /server
>
> *My DSpace configuration is:*
>
> ui:
>   ssl: false
>   host: localhost
>   port: 4000
>   nameSpace: /
>
>   rateLimiter:
> windowMs: 6 # 1 minute
> max: 500 # limit each IP to 500 requests per windowMs
>   useProxies: true
>
> rest:
>   ssl: true
>   host: fevasf-repositorio.ddns.net
>   port: 443
>   nameSpace: /server
>
> Is there any missing configuration? Please help me troubleshoot this 
> issue. 
>
>
>

-- 
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/0556a593-03b1-409d-986c-b585edee7f2bn%40googlegroups.com.

[dspace-tech] Auto media filter for new items

[Andrew K]

Hello!

Is it possible to run filter-media for each new item automatically?

Best regards,
Andrew

-- 
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/87203714-e937-4f2e-afa9-1d747bf43239n%40googlegroups.com.

[dspace-tech] Access control by user agent

[Andrew K]

Hi!

Is it possible to give access to items based on user-agent?

Thanks,
Andrew

-- 
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/22c53713-a5b1-44a8-951d-357d4ada066en%40googlegroups.com.

[dspace-tech] Re: Bulk access management doesn't remove access conditions

[Andrew K]

Has the bulk-access-control process finished successfully? (in the 
Processes tab)

середу, 13 грудня 2023 р. о 18:20:51 UTC+2 Maruan Sahyoun пише:

> I've a question regarding bulk access management and maybe a misconception 
> from my side.
>
> Currentl I have an item with READ permission for Anonymous. Now using Bulk 
> access management I'd like to change that to Administrator using "Replace 
> Access Conditions" and selecting "administrator" from the drop down.
>
> After that I have READ permission for Administrator but still READ 
> permission for Anonymous.
>
> I'm using DSpace 7.6.0 - am I doing something wrong?
>
> BR
> Maruan 
>

-- 
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/95e35f54-3e91-46bd-b746-fd074e5c6134n%40googlegroups.com.

Re: [dspace-tech] Re: Integrate ORCID to DSpace 7 authentication

[Andrew K]

Hey Sean!

That worked! You're a lifesaver! Thanks a lot! 

WBR,
Andrew
вівторок, 5 грудня 2023 р. о 23:47:14 UTC+2 Sean Kalynuk пише:

> Hi Andrew,
>
>  
>
> The public API URL is:
>
>  
>
> https://pub.orcid.org/v3.0
>
>  
>
> The https://api.orcid.org/v3.0 URL is the Member API.
>
>  
>
> -- 
>
> Sean
>
>  
>
> *From: *dspac...@googlegroups.com  on behalf 
> of Andrew K 
> *Date: *Sunday, December 3, 2023 at 2:46 AM
> *To: *DSpace Technical Support 
> *Subject: *[dspace-tech] Re: Integrate ORCID to DSpace 7 authentication
>
> *Caution:* This message was sent from outside the University of Manitoba.
>
>  
>
> dspace log has nothing about it
>
> tomcat log has this for every authentification attempt
>
> 127.0.0.1 - - [03/Dec/2023:10:05:29 +0200] "GET 
> /server/api/authn/orcid?code=KNOI5s HTTP/1.1" 302 -
>
>  
>
> субота, 2 грудня 2023 р. о 20:49:40 UTC+2 Andrew K пише:
>
> Probably worth metnioning that the return URL in browser is 
> https://my.dspace.website/error?status=401=orcid.generic-error
>
> I.e., that might be another error not related to the account email address.
>
>  
>
> And I use public API key.
>
>  
>
> субота, 2 грудня 2023 р. о 20:20:00 UTC+2 Andrew K пише:
>
> Hey guys!
>
>  
>
> I'm having exactly the same problem in 7.6
>
>  
>
> 401unauthorized
> An error occurred during login via ORCID. Make sure you have shared your 
> ORCID account email address with DSpace. If the error persists, contact the 
> administrator
>
>  
>
> My orcid.cfg :
>
>  
>
> #--#
> #ORCID GENERIC CONFIGURATIONS--#
> #--#
> # Configuration with which it is established which user can disconnect a 
> profile from orcid (none, only the admin, only the owner or both).
> # Allowed values are disabled, only_admin, only_owner or admin_and_owner
> orcid.disconnection.allowed-users = admin_and_owner
>
> #--#
> #ORCID CLIENT CONFIGURATIONS---#
> #--#
> # ORCID API (
> https://github.com/ORCID/ORCID-Source/tree/master/orcid-api-web#endpoints)
> #orcid.domain-url= https://sandbox.orcid.org
> orcid.domain-url= https://orcid.org
> orcid.authorize-url = ${orcid.domain-url}/oauth/authorize
> orcid.token-url = ${orcid.domain-url}/oauth/token
> orcid.api-url = https://api.orcid.org/v3.0
> orcid.public-url = https://pub.orcid.org/v3.0
> orcid.redirect-url = ${dspace.server.url}/api/authn/orcid
>
> # ORCID Credentials
> # Your public or member API Credentials, see
> # https://orcid.org/content/register-client-application-0
> # https://info.orcid.org/register-a-client-application-sandbox-member-api/
> orcid.application-client-id = APP-
> orcid.application-client-secret = x-x-xxx-xx
>
> # The scopes to be granted by the user during the login on ORCID (see 
> https://info.orcid.org/faq/what-is-an-oauth-scope-and-which-scopes-does-orcid-support/
> )
> orcid.scope = /authenticate
> #orcid.scope = /read-limited
> #orcid.scope = /activities/update
> #orcid.scope = /person/update
>
>  
>
> I also tried setting email visible to Everyone.
> Interesting that I see in ORCID trusted parties *Access type: Get your 
> ORCID iD* while other trusted parties might have *Access type: Read your 
> information with visibility set to Trusted Parties*.
>
>  
>
> I.e. that looks like DSpace doesn't even ask for the email, right?
>
>  
>
> WBR,
>
> Andrew
>
>  
>
> -- 
> 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/ad35b2a1-8146-47f0-95b8-f38ce33bf0a8n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/dspace-tech/ad35b2a1-8146-47f0-95b8-f38ce33bf0a8n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

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

[dspace-tech] Re: Integrate ORCID to DSpace 7 authentication

[Andrew K]

Hey guys!

I'm having exactly the same problem in 7.6

401unauthorized
An error occurred during login via ORCID. Make sure you have shared your 
ORCID account email address with DSpace. If the error persists, contact the 
administrator

My orcid.cfg :

#--#
#ORCID GENERIC CONFIGURATIONS--#
#--#
# Configuration with which it is established which user can disconnect a 
profile from orcid (none, only the admin, only the owner or both).
# Allowed values are disabled, only_admin, only_owner or admin_and_owner
orcid.disconnection.allowed-users = admin_and_owner

#--#
#ORCID CLIENT CONFIGURATIONS---#
#--#
# ORCID API 
(https://github.com/ORCID/ORCID-Source/tree/master/orcid-api-web#endpoints)
#orcid.domain-url= https://sandbox.orcid.org
orcid.domain-url= https://orcid.org
orcid.authorize-url = ${orcid.domain-url}/oauth/authorize
orcid.token-url = ${orcid.domain-url}/oauth/token
orcid.api-url = https://api.orcid.org/v3.0
orcid.public-url = https://pub.orcid.org/v3.0
orcid.redirect-url = ${dspace.server.url}/api/authn/orcid

# ORCID Credentials
# Your public or member API Credentials, see
# https://orcid.org/content/register-client-application-0
# https://info.orcid.org/register-a-client-application-sandbox-member-api/
orcid.application-client-id = APP-
orcid.application-client-secret = x-x-xxx-xx

# The scopes to be granted by the user during the login on ORCID (see 
https://info.orcid.org/faq/what-is-an-oauth-scope-and-which-scopes-does-orcid-support/)
orcid.scope = /authenticate
#orcid.scope = /read-limited
#orcid.scope = /activities/update
#orcid.scope = /person/update

I also tried setting email visible to Everyone.
Interesting that I see in ORCID trusted parties *Access type: Get your 
ORCID iD* while other trusted parties might have *Access type: Read your 
information with visibility set to Trusted Parties*.

I.e. that looks like DSpace doesn't even ask for the email, right?

WBR,
Andrew

-- 
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/d7d0c94a-7c32-4fe8-8ff2-07303154335en%40googlegroups.com.

[dspace-tech] Re: Integrate ORCID to DSpace 7 authentication

[Andrew K]

Probably worth metnioning that the return URL in browser is 
https://my.dspace.website/error?status=401=orcid.generic-error
I.e., that might be another error not related to the account email address.

And I use public API key.


субота, 2 грудня 2023 р. о 20:20:00 UTC+2 Andrew K пише:

> Hey guys!
>
> I'm having exactly the same problem in 7.6
>
> 401unauthorized
> An error occurred during login via ORCID. Make sure you have shared your 
> ORCID account email address with DSpace. If the error persists, contact the 
> administrator
>
> My orcid.cfg :
>
> #--#
> #ORCID GENERIC CONFIGURATIONS--#
> #--#
> # Configuration with which it is established which user can disconnect a 
> profile from orcid (none, only the admin, only the owner or both).
> # Allowed values are disabled, only_admin, only_owner or admin_and_owner
> orcid.disconnection.allowed-users = admin_and_owner
>
> #--#
> #ORCID CLIENT CONFIGURATIONS---#
> #--#
> # ORCID API (
> https://github.com/ORCID/ORCID-Source/tree/master/orcid-api-web#endpoints)
> #orcid.domain-url= https://sandbox.orcid.org
> orcid.domain-url= https://orcid.org
> orcid.authorize-url = ${orcid.domain-url}/oauth/authorize
> orcid.token-url = ${orcid.domain-url}/oauth/token
> orcid.api-url = https://api.orcid.org/v3.0
> orcid.public-url = https://pub.orcid.org/v3.0
> orcid.redirect-url = ${dspace.server.url}/api/authn/orcid
>
> # ORCID Credentials
> # Your public or member API Credentials, see
> # https://orcid.org/content/register-client-application-0
> # https://info.orcid.org/register-a-client-application-sandbox-member-api/
> orcid.application-client-id = APP-
> orcid.application-client-secret = x-x-xxx-xx
>
> # The scopes to be granted by the user during the login on ORCID (see 
> https://info.orcid.org/faq/what-is-an-oauth-scope-and-which-scopes-does-orcid-support/
> )
> orcid.scope = /authenticate
> #orcid.scope = /read-limited
> #orcid.scope = /activities/update
> #orcid.scope = /person/update
>
> I also tried setting email visible to Everyone.
> Interesting that I see in ORCID trusted parties *Access type: Get your 
> ORCID iD* while other trusted parties might have *Access type: Read your 
> information with visibility set to Trusted Parties*.
>
> I.e. that looks like DSpace doesn't even ask for the email, right?
>
> WBR,
> Andrew
>
>

-- 
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/8587b229-33b7-45b3-bb8f-9f16864bc34dn%40googlegroups.com.

[dspace-tech] Re: Integrate ORCID to DSpace 7 authentication

[Andrew K]

OK, I'm out of options already

I enabled ORCID auth plugin. Set everything correctly in orcid.cfg
initialize-entities - done
create a Collection for "Person" entities - done
config/modules/researcher-profile.cfg - done
config/modules/authority.cfg - done

I am able to create my Researcher Profile. 
But still that 401 error!

Anyone configured ORCID authentification?



-- 
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/7e4861c7-0360-4e99-b067-82c35e971143n%40googlegroups.com.

[dspace-tech] Re: Integrate ORCID to DSpace 7 authentication

[Andrew K]

dspace log has nothing about it
tomcat log has this for every authentification attempt
127.0.0.1 - - [03/Dec/2023:10:05:29 +0200] "GET 
/server/api/authn/orcid?code=KNOI5s HTTP/1.1" 302 -


субота, 2 грудня 2023 р. о 20:49:40 UTC+2 Andrew K пише:

> Probably worth metnioning that the return URL in browser is 
> https://my.dspace.website/error?status=401=orcid.generic-error
> I.e., that might be another error not related to the account email address.
>
> And I use public API key.
>
>
> субота, 2 грудня 2023 р. о 20:20:00 UTC+2 Andrew K пише:
>
>> Hey guys!
>>
>> I'm having exactly the same problem in 7.6
>>
>> 401unauthorized
>> An error occurred during login via ORCID. Make sure you have shared your 
>> ORCID account email address with DSpace. If the error persists, contact the 
>> administrator
>>
>> My orcid.cfg :
>>
>> #--#
>> #ORCID GENERIC CONFIGURATIONS--#
>> #--#
>> # Configuration with which it is established which user can disconnect a 
>> profile from orcid (none, only the admin, only the owner or both).
>> # Allowed values are disabled, only_admin, only_owner or admin_and_owner
>> orcid.disconnection.allowed-users = admin_and_owner
>>
>> #--#
>> #ORCID CLIENT CONFIGURATIONS---#
>> #--#
>> # ORCID API (
>> https://github.com/ORCID/ORCID-Source/tree/master/orcid-api-web#endpoints
>> )
>> #orcid.domain-url= https://sandbox.orcid.org
>> orcid.domain-url= https://orcid.org
>> orcid.authorize-url = ${orcid.domain-url}/oauth/authorize
>> orcid.token-url = ${orcid.domain-url}/oauth/token
>> orcid.api-url = https://api.orcid.org/v3.0
>> orcid.public-url = https://pub.orcid.org/v3.0
>> orcid.redirect-url = ${dspace.server.url}/api/authn/orcid
>>
>> # ORCID Credentials
>> # Your public or member API Credentials, see
>> # https://orcid.org/content/register-client-application-0
>> # 
>> https://info.orcid.org/register-a-client-application-sandbox-member-api/
>> orcid.application-client-id = APP-
>> orcid.application-client-secret = x-x-xxx-xx
>>
>> # The scopes to be granted by the user during the login on ORCID (see 
>> https://info.orcid.org/faq/what-is-an-oauth-scope-and-which-scopes-does-orcid-support/
>> )
>> orcid.scope = /authenticate
>> #orcid.scope = /read-limited
>> #orcid.scope = /activities/update
>> #orcid.scope = /person/update
>>
>> I also tried setting email visible to Everyone.
>> Interesting that I see in ORCID trusted parties *Access type: Get your 
>> ORCID iD* while other trusted parties might have *Access type: Read your 
>> information with visibility set to Trusted Parties*.
>>
>> I.e. that looks like DSpace doesn't even ask for the email, right?
>>
>> WBR,
>> Andrew
>>
>>

-- 
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/ad35b2a1-8146-47f0-95b8-f38ce33bf0a8n%40googlegroups.com.

Re: [dspace-tech] Re: DSpace 7.6 slow server response

[Andrew K]

Hi Mayo!

Sure, I looked to pm2 first thing
This is what I have
[image: 2023-11-15_171420.png]
I guess it's OK, cluster mode.
I added "exec_mode": "cluster" in dspace-ui-json
I also use "pm2 start /home/dspace/dspace-angular-dspace-7.6/dspace-ui.json 
-i max"
Per your advice I am going to change it to a number less than cores #. As 
soon as know how much cores I can get)

Based on my understanding, once the page loads, it runs in your browser. 
Only when you refresh,
open it on new window (or for some other reason download the whole page 
from server) is it slow.
When it is downloaded and runs in browser, it only executes some calls to 
backend, which is fast.
This would agree with your observations.


Ah. Thanks! That explains a lot.
But then I can not understand the main page loading so long *when the anon 
cache is enabled*.
The main page should be cached 100%.
But it always loads as if there's no cache... It actually looks like it 
loads as long as for a logged user.
I have 
 anonymousCache:
  max: 50
  timeToLive: 720 # 3 hours
  allowStale: true

That should work, right?

Best regards,
Andrew

-- 
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/c5c92992-7a5f-4efa-abb6-7d6a55e43341n%40googlegroups.com.

Re: [Extern] Re: [dspace-tech] Re: DSpace 7.6 slow server response

[Andrew K]

Hi Majo!

Thanks again for your help.
Actually right now the server works with 3 pm2 instances on 4 CPU cores and 
6GB RAM. Not too fast, but still not choking.
I also blocked Amazonbot (10-20K connections a day) and a couple of less 
active bots. It helped a lot.
Looks like 5-7 instances is pretty much enough for a modest repository like 
ours (13K items).
Thus 8-10 CPU cores should do the job. As for RAM amount, it's never too 
much, but 10-12GB should be OK (on our VDS hosting RAM is a lot more 
expensive, 1GB RAM equals 10 CPU cores).

Best regards,
Andrew

понеділок, 20 листопада 2023 р. о 08:59:24 UTC+2 dataquest пише:

> Hi Andrew.
>
> Glad I could help.
> Certainly heed advice from Michael and don't overdo it with the instances.
> Your issue was that there was a single one.. that will never be enough.
> But 5 might be, or 7.. Impossible to say. 11 appears to be too much.
> Now that you know how to set it, perhaps try experimenting a bit,
> so that you can find the correct number for you. Too many instances
> will drain your memory, cause swapping and definitely slow things down.
>
> Best regards,
> Majo
>
> On Thu, Nov 16, 2023 at 6:07 PM Plate, Michael <
> pl...@bibliothek.uni-kassel.de> wrote:
>
>> Hi Andrew,
>>
>> be careful on the number of CPUs (Cores) you assign to the VM - this may 
>> be a boomerang if the host can't get enough free Cores in one piece and 
>> your VM has to wait until the amount of configured Cores is free.
>> At least in former times this was limitation, I'am not sure if this still 
>> is that way.
>>
>> CU
>>
>> Michael
>>
>> 
>> Von: dspac...@googlegroups.com  im Auftrag 
>> von Andrew K 
>> Gesendet: Donnerstag, 16. November 2023 17:29
>> An: DSpace Technical Support
>> Betreff: [Extern] Re: [dspace-tech] Re: DSpace 7.6 slow server response
>>
>> […]
>>
>> -- 
>> 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/a70d1abf85394d9f856ebd3e4f99a389%40bibliothek.uni-kassel.de
>> .
>>
>

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

Re: [Extern] Re: [dspace-tech] Re: DSpace 7.6 slow server response

[Andrew K]

Hi Michael!

Thanks for the warning! I'm not sure what kind of virtualization we're on. 
But probably it also has this problem, as they say that the usual amount is 
4 cores per server.
I guess the performance suffers more with full load (which is rare in this 
case). 
Still, even it it doesn't scale linear, 8 cores should overperform 4 cores, 
right?

Best regards,
Andrew

четвер, 16 листопада 2023 р. о 19:07:18 UTC+2 Plate, Michael пише:

> Hi Andrew,
>
> be careful on the number of CPUs (Cores) you assign to the VM - this may 
> be a boomerang if the host can't get enough free Cores in one piece and 
> your VM has to wait until the amount of configured Cores is free.
> At least in former times this was limitation, I'am not sure if this still 
> is that way.
>
> CU
>
> Michael
>
> 
> Von: dspac...@googlegroups.com  im Auftrag von 
> Andrew K 
> Gesendet: Donnerstag, 16. November 2023 17:29
> An: DSpace Technical Support
> Betreff: [Extern] Re: [dspace-tech] Re: DSpace 7.6 slow server response
>
> […]

-- 
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/77e3f7b6-36da-4eb7-a51b-6636d42e1f60n%40googlegroups.com.

Re: [dspace-tech] Re: DSpace 7.6 slow server response

[Andrew K]

Hi Hrafn!

Thanks! I am also somewhat hopeful about the new release. In my situation 
first thing I looked for were fixed performance issues )

Best regards,
Andrew

четвер, 16 листопада 2023 р. о 15:32:46 UTC+2 Hrafn Malmquist пише:

> Hi guys
>
> I would consider upgrading to 7.6.1. There are a few performance fixes in 
> this bug release:
>
> https://wiki.lyrasis.org/display/DSDOC7x/Release+Notes#ReleaseNotes-7.6.1ReleaseNotes
>
> Specifically https://github.com/DSpace/dspace-angular/issues/2482. A bug 
> where a page load would make 1 or 2 unnecessary GET calls to the server 
> depending on the path. Upgrading to 7.6.1 should therefore reduce server 
> load.
>
> Best regards, Hrafn
>
> On Wed, Nov 15, 2023 at 3:48 PM Andrew K  wrote:
>
>> Hi Mayo!
>>
>> Sure, I looked to pm2 first thing
>> This is what I have
>> [image: 2023-11-15_171420.png]
>> I guess it's OK, cluster mode.
>> I added "exec_mode": "cluster" in dspace-ui-json
>> I also use "pm2 start 
>> /home/dspace/dspace-angular-dspace-7.6/dspace-ui.json -i max"
>> Per your advice I am going to change it to a number less than cores #. As 
>> soon as know how much cores I can get)
>>
>> Based on my understanding, once the page loads, it runs in your browser. 
>> Only when you refresh,
>> open it on new window (or for some other reason download the whole page 
>> from server) is it slow.
>> When it is downloaded and runs in browser, it only executes some calls to 
>> backend, which is fast.
>> This would agree with your observations.
>>
>>
>> Ah. Thanks! That explains a lot.
>> But then I can not understand the main page loading so long *when the 
>> anon cache is enabled*.
>> The main page should be cached 100%.
>> But it always loads as if there's no cache... It actually looks like it 
>> loads as long as for a logged user.
>> I have 
>>  anonymousCache:
>>   max: 50
>>   timeToLive: 720 # 3 hours
>>   allowStale: true
>>
>> That should work, right?
>>
>> Best regards,
>> Andrew
>>
>> -- 
>>
> 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/c5c92992-7a5f-4efa-abb6-7d6a55e43341n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/dspace-tech/c5c92992-7a5f-4efa-abb6-7d6a55e43341n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

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

[dspace-tech] Re: DSpace 7 localization issue

[Andrew K]

Hi Tim!

Thank you!
Looking deeper into this issue, I found this topic "Syncing existing 
translations with changes to en.json5"
https://wiki.lyrasis.org/pages/viewpage.action?pageId=117735441#DSpace7TranslationInternationalization(i18n)Localization(l10n)-Syncingexistingtranslationswithchangestoen.json5

I just run *yarn run sync-i18n* and magically received fully updated 
localization file synced to the authoritative English file. 
Moreover, all translated keys I had added before were kept!
So I highly recommend this tool. It completely solves the problem of 
missing keys.

Best regards,
Andrew



четвер, 16 листопада 2023 р. о 00:56:22 UTC+2 DSpace Technical Support пише:

> Hi Andrew,
>
> We're aware that these i18n files can get "out of sync" easily and are 
> working on ways to improve that.  See this ticket: 
> https://github.com/DSpace/dspace-angular/issues/2340
>
> There's no exact solution yet, but many developers agree it's a 
> frustration.  So, if you have more ideas to share, feel free to add to that 
> ticket.
>
> Regarding the display of missing keys, the current behavior is the same as 
> it was in DSpace 6.x (where the key was displayed if missing).  I'm not 
> aware of a way to change that to be English by default, but you are welcome 
> to create a ticket regarding that and I can ask other developers to look 
> into it.  I agree that it might be better to show English instead of a 
> (cryptic) i18n key.
>
> Tim
>
> On Tuesday, November 7, 2023 at 8:18:21 AM UTC-6 Andrew K wrote:
>
>> Hello!
>>
>> I noticed that the localization files lag behind. And this is perfectly 
>> normal.
>> The documentation says: "*When new keys are introduced, TODO messages 
>> are automatically added to the catalogs of other languages*" 
>>
>> https://wiki.lyrasis.org/pages/viewpage.action?pageId=117735441#DSpace7TranslationInternationalization(i18n)Localization(l10n)-Translations(forexample,nl.json5)
>> But that does not happen, new keys are missing, at least for uk.json5. Is 
>> there a way to correct that?
>>
>> And the next problem is that missing keys in the .json5 file are 
>> displayed as key names. It would be much much better if the English names 
>> were shown instead.
>> Is that possible?
>>
>> Best regards,
>> Andrew
>>
>> P.S.: 
>>
>

-- 
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/f1891fad-1dd6-4f93-a256-9905c285804dn%40googlegroups.com.

Re: [dspace-tech] Re: DSpace 7.6 slow server response

[Andrew K]

Hey Majo!

You're a lifesaver! Of course I had one pm2 instance! Now I have 11 of them 
and the server is doing a lot better!
[image: 2023-11-16_182827.png]
Still, the response in not instant. I think the response time depends on 
the performance of one pm2 instance and one CPU core (which is not the best 
in my case).
But at least the server is not chocking with multiple requests. That is a 
very big deal! Amazing. Thank you!
The speed index is 1-2s now instead of 5s! That is acceptable.

Best regards,
Andrew
четвер, 16 листопада 2023 р. о 15:47:21 UTC+2 dataquest пише:

> Hi, it is me again! 
>
> Hrafn, there are many many many REST calls every time any page loads. I do 
> not think the issue will be mitigated
> by the update you mention.
>
> Andrew, your pm2 configuration does not seem to be correct at all. 
> I have 7 nodes and it looks like this:
> [image: image.png]
> From what you posted, it seems you only have one node running, which would 
> explain a lot.
> I am not sure if you are using dspace-ui.json (or similar) config file for 
> pm2, if so, check if you have
> line such as this:
> "instances": "7"
> I know the -i parameter on command line should set this and I have no idea 
> why you apparently only have
> one node, but it might be a good idea to try this. I also found that for 
> certain settings, I have to do
> pm2 delete dspace-ui.json
> and then
> pm2 start dspace-ui.json
>
> merely using pm2 restart dspace-ui.json was not sufficient, perhaps that 
> is what happened.
>
> The anon chache only starts having effect, if your server is not clogged 
> up by other requests. If it is,
> requests that could be served from cache will probably spend some time 
> waiting, therefore being slow
> anyway.
>
> Time to live = 3 hours is way too long, I have 10 seconds and it is fine.
>
> In my humble opinion, your biggest problem is only having one node on pm2. 
> If you do not resolve that, I wouldn't expect other fixes to have much 
> effect on anything.
>
> Make sure you see several nodes listed, just like in my screenshot. Then 
> you can start looking
> into other optimizations.
>
> Best regards,
> Majo
>
>
>
> On Thu, Nov 16, 2023 at 2:32 PM Hrafn Malmquist  
> wrote:
>
>> Hi guys
>>
>> I would consider upgrading to 7.6.1. There are a few performance fixes in 
>> this bug release:
>>
>> https://wiki.lyrasis.org/display/DSDOC7x/Release+Notes#ReleaseNotes-7.6.1ReleaseNotes
>>
>> Specifically https://github.com/DSpace/dspace-angular/issues/2482. A bug 
>> where a page load would make 1 or 2 unnecessary GET calls to the server 
>> depending on the path. Upgrading to 7.6.1 should therefore reduce server 
>> load.
>>
>> Best regards, Hrafn
>>
>> On Wed, Nov 15, 2023 at 3:48 PM Andrew K  wrote:
>>
>>> Hi Mayo!
>>>
>>> Sure, I looked to pm2 first thing
>>> This is what I have
>>> [image: 2023-11-15_171420.png]
>>> I guess it's OK, cluster mode.
>>> I added "exec_mode": "cluster" in dspace-ui-json
>>> I also use "pm2 start 
>>> /home/dspace/dspace-angular-dspace-7.6/dspace-ui.json -i max"
>>> Per your advice I am going to change it to a number less than cores #. 
>>> As soon as know how much cores I can get)
>>>
>>> Based on my understanding, once the page loads, it runs in your browser. 
>>> Only when you refresh,
>>> open it on new window (or for some other reason download the whole page 
>>> from server) is it slow.
>>> When it is downloaded and runs in browser, it only executes some calls 
>>> to backend, which is fast.
>>> This would agree with your observations.
>>>
>>>
>>> Ah. Thanks! That explains a lot.
>>> But then I can not understand the main page loading so long *when the 
>>> anon cache is enabled*.
>>> The main page should be cached 100%.
>>> But it always loads as if there's no cache... It actually looks like it 
>>> loads as long as for a logged user.
>>> I have 
>>>  anonymousCache:
>>>   max: 50
>>>   timeToLive: 720 # 3 hours
>>>   allowStale: true
>>>
>>> That should work, right?
>>>
>>> Best regards,
>>> Andrew
>>>
>>> -- 
>>> 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" gro

[dspace-tech] Re: DSpace 7.6 slow server response

[Andrew K]

OK, I suddenly realized that DSpace log works only when I run scripts like 
index-discovery, filter-media etc. Nothing on the web activity

So, the latest description of the problem:
Any page loads for a very long time, like 30s. But when it's loaded, the 
navigation works pretty fast within the browser tab: search, collections, 
statistics.
Reloading or opening a link in a new tab causes very slow loading again.
Please help me figure it 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/a72cafa0-be53-42a0-adf1-7bcc3eb204d6n%40googlegroups.com.

[dspace-tech] Re: DSpace 7.6 slow server response

[Andrew K]

OK, that looks like the cache. When I set 
anonymousCache:
  max: 0
I stopped getting "Error fetching item".
At least the page loads now. It takes 30s to load (!), but at least no 
error.
I think Google is going to ban our server with such response times, 
though...
понеділок, 13 листопада 2023 р. о 20:38:51 UTC+2 Andrew K пише:

> Another very interesting observation.
> I load the main page. It takes a while. Then I click the links, everything 
> works perfectly, list the items by date, list the communities... everything.
> So, I find some item and open it (works pretty fast again, all in the same 
> tab). Then I copy the link and insert it to the new tab, press Enter. 
> And boom! Error fetching item   But how?? Why??? The same happens when I 
> simply refresh the page...
>
> Something is fundamentally wrong. But what? While dspace log is not 
> working, I can only guess...
>
>
>

-- 
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/945ed83d-e084-424e-aede-13062a0b41a7n%40googlegroups.com.

Re: [dspace-tech] Re: DSpace 7.6 slow server response

[Andrew K]

Dear Majo!

Thanks a lot for your reply!

It clears a lot: DSpace 7 needs a lot of CPU power.

Yes, I was really desperate because I spent a lot of time (not without 
interest and pleasure, though) setting up the new server. And our current 
hosting provider has pretty slow VDS: CPU about 2GHz, slow disk etc. But 
it's affordable and we already use it. Switching to a different one is a 
huge PITA. On the other hand, we need VDS because the power outages 
expected in winter, so it is going to be hard to keep our local servers 
powered 24/7.

So, what I did first is increased the VDS's number of CPU cores from 4 to 
8. And it helped significantly. The server is more stable, the response 
times shortened. The server load is usually <1 instead of ~1.5. Now the 
server (more or less) works.
But still, it happens to throw error pages. Sometines Apache proxy says it 
received no data. And the page loading in a new browser tab is always 
delayed. On the other hand, within one tab all possible links work fast.
About the anonymousCache, I tried setting it to 100. But there were errors 
too often. So I turned it off. Less errors. Now I set it to 20. Works so 
far...

Also, PageSpeed Insights show pretty awful results, Speed Index about 5s 
for desktop. But at least it shows something, the server barely responded 
before.
I just tested a few other DSpace 7 repos with PageSpeed Insights, and they 
all show low efficiency and high First Contentful Paint time.

So, what I can and plan to do is increase the number of cores to 12. That 
should speed it up a little more.
Then I suppose we all should wait for DSpace to get more optimized )

Thanks again!

Best regards,
Andrew





вівторок, 14 листопада 2023 р. о 09:50:36 UTC+2 dataquest пише:

> Dear Andrew.
>
> I faced similar problems when we deployed our first instance of DSpace and 
> I 
> was also quite confused so as to what is wrong.
>
> Perhaps most important question is, if you are using pm2 with several 
> nodes.
> When I was deploying it, performance did mention it, but we weren't using 
> it at first.
> You certainly need it (pm2 starts several nodes, so frontend is served from
> multiple threads, not just one).
>
> Also having anonymousCache set to 0 is probably the issue. I tuned it for 
> some time,
> but certainly use at least 10, so that some requests are much faster and 
> your server
> does not get clogged up, therefore slowing every load.
>
> If you needed to set it to 0 in order for everything to work, there must 
> be some other,
> worse problem. Perhaps insufficient memory?
>
> Also, your server spec seem to be too low. It seems SSR requires much 
> "bigger" server.
> We are using 15 cores, 32GB RAM and it is about fine (10 cores were ok, 
> but not when
> there were long imports of many items running etc.) Yes, it requires much 
> more resources
> than previous versions, but that simply seems to be the case...
>
> I am no expert, so far I only deployed one instance, but I learned a lot 
> with it, at least
> compared to what I knew before. (If I wrote anything inaccurate I am 
> sorry, anybody
> that knows better, please correct me.) But I know I was quite desperate 
> and I hope
> this can help you a bit.
>
> To reiterate, most important things (in my opinion) are:
> 1. Make sure you are using pm2, without it it will hardly ever work well 
> (and fast enough)
> 2. I suppose your server specs are insufficient.
>
>
> Best regards,
> Majo
>
> On Mon, Nov 13, 2023 at 9:43 PM Andrew K  wrote:
>
>> OK, I suddenly realized that DSpace log works only when I run scripts 
>> like index-discovery, filter-media etc. Nothing on the web activity
>>
>> So, the latest description of the problem:
>> Any page loads for a very long time, like 30s. But when it's loaded, the 
>> navigation works pretty fast within the browser tab: search, collections, 
>> statistics.
>> Reloading or opening a link in a new tab causes very slow loading again.
>> Please help me figure it 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...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dspace-tech/a72cafa0-be53-42a0-adf1-7bcc3eb204d6n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/dspace-tech/a72cafa0-be53-42a0-adf1-7bcc3eb204d6n%40googlegroups.com?utm_medium=email_source=footer>
>&g

[dspace-tech] Re: the filter values on the home page

[Andrew K]

Hello Alex

You need to enable webui.strengths.show in dspace.cfg
It is available in DSpace 7.6.

WBR,
Andrew
вівторок, 14 листопада 2023 р. о 10:08:32 UTC+2 Alex B пише:

> Dear colleagues, please help me display the filter values on the home page.
>
> For example -
>
> [image: Screenshot from 2023-11-14 11-06-15.png]
> what steps need to be taken for this?
>
> Best regards,
> Alex
>

-- 
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/76815544-ab8d-4aae-8a10-f0acc9541739n%40googlegroups.com.

[dspace-tech] DSpace 7.6 slow server response

[Andrew K]

Hello!

Yesterday I put a new DSpace 7.6 server to production.
And unfortunately there are some weird problems.
1. Often the server response time is very high, like 4-6s. But the server 
load is about 1.5, one process (node /home/dspa) has 100-150% load. Also 
iotop shows no significant load (less than 100-300K/s, mostly 0 at all).
2. Sometimes red error boxes pop like *0 Http failure response for 
/server/api/core/bundles/c6beb8dd-b676-4099-8b3e-e382addabe9a/bitstreams?page=0=5:
 
0 Unknown Error*. Also error page 502 is frequent.
3. Apache error log has something like 

*[Mon Nov 13 16:17:32.347870 2023] [proxy:error] [pid 1724:tid 
140175577442048] [client 87.250.224.227:64062] AH00898: Error reading from 
remote server returned by /bitstream/123456789/3767/1/Prioritetni 
sotsial\xca\xb9ni spozhyvy.pdf[Mon Nov 13 16:17:35.984410 2023] 
[proxy_http:error] [pid 1864:tid 140176072349440] (104)Connection reset by 
peer: [client 47.128.18.32:52936] AH01102: error reading status line from 
remote server localhost:4000*



*[Mon Nov 13 00:23:50.983739 2023] [proxy_http:error] [pid 10447:tid 
139668360255232] (104)Connection reset by peer: [client 
185.191.171.19:54166] AH01102: error reading status line from remote server 
localhost:4000[Mon Nov 13 00:23:50.983789 2023] [proxy:error] [pid 
10447:tid 139668360255232] [client 185.191.171.19:54166] AH00898: Error 
reading from remote server returned by 
/handle/123456789/1345/simple-search[Mon Nov 13 00:26:13.310238 2023] 
[proxy_http:error] [pid 10447:tid 139667739490048] (104)Connection reset by 
peer: [client 47.128.52.192:41852] AH01102: error reading status line from 
remote server localhost:4000, referer: /st>[Mon Nov 13 00:26:13.310299 
2023] [proxy:error] [pid 10447:tid 139667739490048] [client 
47.128.52.192:41852] AH00898: Error reading from remote server returned by 
/assets/images/logo.png, referer: /statistics/items/b991c0e>[Mon Nov 13 
00:28:08.645601 2023] [proxy_http:error] [pid 10447:tid 139668493174528] 
(70007)The timeout specified has expired: [client 52.167.144.216:43793] 
AH01102: error reading status line from remote server localhost:4000*
4. Dspace log is unavailable! The last logged time is yesterday evening. 
Since then there's no log. I have not changed any log settings.

I 
followed https://wiki.lyrasis.org/display/DSDOC7x/Performance+Tuning+DSpace 
pretty thoroughly. The DSpace server is on the VDS and it works through 
apache proxy (for https).

This is very disappointing. The old server worked lke a charm, always 
instant response. 
Please help me trace the source of errors.

WBR,
Andrew

PS: That said, once the page has loaded, clicking the links like statistics 
always has instant responce (cache?). But opening links in another tab 
takes forever, or fails

-- 
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/9714aa57-bcad-477d-89d2-afbecab0d954n%40googlegroups.com.

[dspace-tech] Re: DSpace 7.6 slow server response

[Andrew K]

I forgot to mention the server capacity: 4 cores, 6GB RAM (12GB doesn't 
change a lot), 200GB.

-- 
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/ac840440-ea37-4759-b464-5c79fea4c27an%40googlegroups.com.

Re: [dspace-tech] Re: DSpace 7.6 slow server response

[Andrew K]

Hello Hrafn,

It was 5.4 (it actually still is, I only switched DNS to the new server).
But the old server had no https, unfortunately.

понеділок, 13 листопада 2023 р. о 16:48:51 UTC+2 Hrafn Malmquist пише:

> Hello Andrew
>
> Out of curiosity, what version was the old server that worked like a charm?
>
> Hrafn
>
> On Mon, Nov 13, 2023 at 2:42 PM Andrew K  wrote:
>
>> I forgot to mention the server capacity: 4 cores, 6GB RAM (12GB doesn't 
>> change a lot), 200GB. 
>>
>> -- 
>> 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/ac840440-ea37-4759-b464-5c79fea4c27an%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/dspace-tech/ac840440-ea37-4759-b464-5c79fea4c27an%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

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

[dspace-tech] Re: DSpace 7.6 slow server response

[Andrew K]

Another very interesting observation.
I load the main page. It takes a while. Then I click the links, everything 
works perfectly, list the items by date, list the communities... everything.
So, I find some item and open it (works pretty fast again, all in the same 
tab). Then I copy the link and insert it to the new tab, press Enter. 
And boom! Error fetching item   But how?? Why??? The same happens when I 
simply refresh the page...

Something is fundamentally wrong. But what? While dspace log is not 
working, I can only guess...


-- 
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/8e748a56-aa9d-4673-ba2c-af5925a3b510n%40googlegroups.com.

[dspace-tech] Re: Anthropic’s ClaudeBot is aggressively scraping DSpace

[Andrew K]

Yes, pretty aggressively, Stats for today:
*78575 Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; 
ClaudeBot/1.0; +claude...@anthropic.com)*
Googlebot is the next in the top crawlers with decent 5500 requests.
But I've seen worse load.
пʼятницю, 26 квітня 2024 р. о 18:51:54 UTC+3 James Holobetz пише:

> Has anyone in the DSpace community/tech seen a large spike in queries 
> for Anthropic’s ClaudeBot?
>
> User Agent: compatible; "ClaudeBot/1.0; +claudebot\@anthropic.com"
>
> Here is some other references lately:
>
>
> https://www.reddit.com/r/singularity/comments/1cdm97j/anthropics_claudebot_is_aggressively_scraping_the/
>
> We have been getting hit hard for a couple days now.
>
> Best regards,
>
> James
>
>

-- 
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/4afce327-06bf-4ccf-ac78-80a4db488b58n%40googlegroups.com.

Re: [dspace-tech] Re: Dspace IP Authorization for particular collection

[Andrew K]

Hi,
There's this tab "Access Control".
I use "local" group for local IPs, then I set permissiont for this group to 
access bitstreams (files) or metadata (items).
WBR,
Andrew
[image: 2024-05-15_175719.png]

середу, 15 травня 2024 р. о 17:44:53 UTC+3 Young, Philip пише:

> I did this recently for an item but it looks like you could do it for a 
> collection as well.  For an item, Edit > Status > Authorizations and the 
> first policy should be the item policy, where you can change Anonymous to 
> your IP group.  Then the item should be visible only to that group, but not 
> the public.   For a collection, I have not tested it, but try Edit > 
> Authorizations to edit the groups.  Or try Access Control and apply a 
> condition to the metadata.  In this case there may be some work to get your 
> IP group listed as one of the access conditions in the drop-down.
>
> Philip
> --
> *From:* dspac...@googlegroups.com  on behalf 
> of Julia Gilmore 
> *Sent:* Monday, May 13, 2024 10:26 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Re: Dspace IP Authorization for particular 
> collection 
>  
> Hi all,  
>
> Following up on Salony's question - we are also wondering if its possible 
> to require authorization to view a specific collection, and how we would go 
> about setting that up? 
>
> Our use case: Requiring student Id login via Shibboleth authentication to 
> view a test bank. 
>
> Suggestion: Any students that login via Shibboleth are assigned to a user 
> group that has read access for the collection. Not sure if this is the way 
> to go about it though!
>
> Any guidance would be appreciated. 
>
> Thank you, 
>
> Julia
>
> On Wednesday 3 January 2024 at 11:04:23 UTC-5 Salony Permanand wrote:
>
> Hello All,
>
> I am using DSpace 7.6
>
> I want to access restrict to particular collection for the general public, 
> but if a user visits from an on-campus IP address, they can download/view 
> the files.
>
> For that I created a group named ipdata and provide authorization to that. 
> Attached screnshot below
>
> I havn't added any user to group
>
> from *authentication.cfg*
> plugin.sequence.org.dspace.authenticate.AuthenticationMethod = 
> org.dspace.authenticate.IPAuthentication
> and from *authentication-ip.cfg*
> authentication-ip.ipdata = 1.2.3.4
>
> Now If I want to access that collection from any  ip other than 1.2.3.4 , 
> then it is showing all data. I also created new items after changes , that 
> also not helped
>
>  How will I restrict all ip's other than required
>
> Any help is highly appreciated   
>
> Salony Permanand 
> *Mob: 7275838206 <(727)%20583-8206>*
>
> -- 
> 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/336887d4-e6ee-4232-943b-0f36103e1e8bn%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/75c7686f-5ed5-477b-8364-0a446ab8286en%40googlegroups.com.

[dspace-tech] Re: Direct URLs to documents in bitstream store in DSpace 7?

[Andrew K]

Hi Tim,

Unfortunately not all links are redirected automatically.
Links with spaces or cyrillic symbols in the filename fail to open.

Best regards,
Andrew

середу, 6 березня 2024 р. о 17:44:00 UTC+2 DSpace Technical Support пише:

> Hi Sean,
>
> Correct, DSpace 7 will only display/show the links like:  
> https://institution.ca/bitstreams/4d83d6df-7914-4cd2-b4f3-197a776ccec3/download
>
> However, older links (like those from DSpace 6) should **redirect 
> automatically** to the new location.  So, no old links should break during 
> an upgrade.
>
> Tim
>
> On Wednesday, February 28, 2024 at 10:55:52 AM UTC-6 McLaughlin, Sean 
> (BAC/LAC) wrote:
>
>> Hello,
>>
>>  
>>
>> Can anyone confirm if direct links to assets are still available, for 
>> example to be exposed in a metadata harvest, in DSpace 7? 
>>
>>  
>>
>> In previous versions of DSpace we were able to extract direct links to 
>> say, PDFs, from metadata, that would appear such as "
>> http://institution.ca/bitstream//xx/*document.pdf*> >"
>>
>>  
>>
>> and now I am seeing only things like
>>
>>
>> https://institution.ca/bitstreams/4d83d6df-7914-4cd2-b4f3-197a776ccec3/download
>>
>>  
>>
>> I read the support documentation but did not see a clear answer--are the 
>> latter type of links the only ones provided for in DSpace 7?
>>
>>  
>>
>> Thank you,
>>
>>  
>>
>> Sean
>>
>

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

[dspace-tech] Re: Cleanup (7.6) bombs with error message

[Andrew K]

For clarity, the error is
*Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on 
table "bitstream" violates foreign key constraint 
"requestitem_bitstream_id_fkey" on table "requestitem"*

*  Detail: Key (uuid)=(15b3ebc4-ae05-461e-ab9d-3a39bdb1bb50) is still 
referenced from table "requestitem".*
неділю, 17 березня 2024 р. о 16:07:38 UTC+2 Andrew K пише:

Hi!
I have the same error on cleanup. Trying to use this method to fix it.
But I receive 2 empty rows here instead of some uuids


*\set a 15b3ebc4-ae05-461e-ab9d-3a39bdb1bb50 dspace=# SELECT item_id AS b 
FROM requestitem WHERE bitstream_id = :'a';*b
- - -


(2 rows)

This looks OK though
*dspace=# SELECT deleted FROM bitstream WHERE uuid = :'a';*
deleted
-
t
(1 row)

What do I do next?

Thanks,
Andrew

-- 
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/d1c689e1-4080-4dc3-8fde-9a3739af0fe8n%40googlegroups.com.

[dspace-tech] Re: Cleanup (7.6) bombs with error message

[Andrew K]

Hi!
I have the same error on cleanup. Trying to use this method to fix it.
But I receive 2 empty rows here instead of some uuids


*\set a 15b3ebc4-ae05-461e-ab9d-3a39bdb1bb50 dspace=# SELECT item_id AS b 
FROM requestitem WHERE bitstream_id = :'a';*b
- - -


(2 rows)

This looks OK though
*dspace=# SELECT deleted FROM bitstream WHERE uuid = :'a';*
deleted
-
t
(1 row)

What do I do next?

Thanks,
Andrew
середу, 5 липня 2023 р. о 09:29:31 UTC+3 Technologiczny Informator пише:

> Hi,
>
> Mark was replying to my post then. While cleaning I had the same one case 
> as yours. Since you got to know Mark's method, I'm throwing you my 
> "procedure" without comment:
>
> *ERROR: update or delete on table "bitstream" violates foreign key 
> constraint "requestitem_bitstream_id_fkey" on table "requestitem"*
> *  Szczegóły: Key (uuid)=(e2f6374b-f2ff-435c-9940-f37adc6250aa) is still 
> referenced from table "requestitem".*
>
> *\set a e2f6374b-f2ff-435c-9940-f37adc6250aa*
> *SELECT item_id AS b FROM requestitem WHERE bitstream_id = :'a';*
>
> *b*
> *--*
> * db43aa8e-855d-42b9-b82c-57c3d469e4f7*
> db43aa8e-855d-42b9-b82c-57c3d469e4f7
> (2 rows)
>
> *SELECT deleted FROM bitstream WHERE uuid = :'a';*
> deleted
> -
> t
> (1 row)
>
> *\set b* *db43aa8e-855d-42b9-b82c-57c3d469e4f7*
> *UPDATE requestitem SET bitstream_id = null WHERE item_id = :'b';*
> UPDATE 2
>
> \q
>
> Regards,
> Mariusz
> poniedziałek, 3 lipca 2023 o 20:08:03 UTC+2 Wally Grotophorst napisał(a):
>
>> I saw the earlier posting on a problem with cleanup that stopped running 
>> with a message like this one:
>>
>>  Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on 
>> > table "bitstream" violates foreign key constraint 
>> > "bundle_primary_bitstream_id_fkey" on table "bundle" 
>> > Detail: Key (uuid)=(02caead4-de93-4011-8105-0e6921f286d8) is still 
>> > referenced from table "bundle". 
>>
>> I have the same issue with 7.6 and the suggestions Mark Wood included in 
>> response on June 12 has been working for me.  Well, sort of.  I fixed 9 or 
>> 10 using Mark's method and then cleanup died with this error message:
>>
>> Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on 
>> table "bitstream" violates foreign key constraint 
>> "requestitem_bitstream_id_fkey" on table "requestitem"
>>
>>   Detail: Key (uuid)=(ca1a4a1e-5fd0-418e-96f6-6911475a8b2f) is still 
>> referenced from table "requestitem".
>>
>> Mark's suggestion does not work for this table but I wonder if someone 
>> else has encountered this issue and has the SQL that might fix it?  Thanks.
>>
>> - Wally Grotophorst
>> George Mason University
>>
>>
>>  
>>
>

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

[dspace-tech] Re: Cleanup (7.6) bombs with error message

[Andrew K]

Hi Amy!

Not that I completely understand it, but I run
*dspace=# \set a 15b3ebc4-ae05-461e-ab9d-3a39bdb1bb50*





*dspace=# SELECT requestitem_id AS b FROM requestitem WHERE bitstream_id = 
:'a'; b--- 2 3(2 rows)*
and then



*dspace=# UPDATE requestitem SET bitstream_id = null WHERE requestitem_id = 
2;UPDATE 1dspace=# UPDATE requestitem SET bitstream_id = null WHERE 
requestitem_id = 3;UPDATE 1*
Problem solved! Thanks a lot!
Cleanup successfully finished now.

WBR,
Andrew



четвер, 21 березня 2024 р. о 22:43:11 UTC+2 Amy Ball Wicklund пише:

> You could try substituting requestitem_id for item_id in those same 
> queries. It's the Primary Key in the requestitem table, and thus cannot be 
> empty, so you should get 2 unique values that you can use to update the 
> records. You will just have to run the update query for each value returned.
>
> On Sunday, March 17, 2024 at 8:21:46 AM UTC-7 Andrew K wrote:
>
>> For clarity, the error is
>> *Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on 
>> table "bitstream" violates foreign key constraint 
>> "requestitem_bitstream_id_fkey" on table "requestitem"*
>>
>> *  Detail: Key (uuid)=(15b3ebc4-ae05-461e-ab9d-3a39bdb1bb50) is still 
>> referenced from table "requestitem".*
>> неділю, 17 березня 2024 р. о 16:07:38 UTC+2 Andrew K пише:
>>
>> Hi!
>> I have the same error on cleanup. Trying to use this method to fix it.
>> But I receive 2 empty rows here instead of some uuids
>>
>>
>> *\set a 15b3ebc4-ae05-461e-ab9d-3a39bdb1bb50 dspace=# SELECT item_id AS b 
>> FROM requestitem WHERE bitstream_id = :'a';*b
>> - - -
>>
>>
>> (2 rows)
>>
>> This looks OK though
>> *dspace=# SELECT deleted FROM bitstream WHERE uuid = :'a';*
>> deleted
>> -
>> t
>> (1 row)
>>
>> What do I do next?
>>
>> Thanks,
>> Andrew
>>
>>

-- 
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/94075d72-2b10-4cb7-84ff-af042618a163n%40googlegroups.com.

[dspace-tech] PM2 error: dspace-ui > 1 rules skipped due to selector errors

[Andrew K]

Hi!
I started using pm2 monit and found that every process constantly throws 
this error:

*dspace-ui > 1 rules skipped due to selector errors:   
dspace-ui > 
.custom-file-input:lang(en)~.custom-file-label -> unmatched pseudo-class 
:lang*
What is the problem? How to solve it?

WBR,
Andrew

-- 
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/8ca0d719-062a-4a9a-9b97-1adfbc125842n%40googlegroups.com.

Re: [dspace-tech] Re: Item Counters for Communities and Collections not working well

[Andrew K]

It shows eactly 2 items now...


середу, 28 лютого 2024 р. о 15:05:45 UTC+2 Caty пише:


This collection has 2 items (one existent and one added by me), but it 
shows collection item counter 1:  "Coleção de teste (1)"

-- 
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/c56a0cb5-3f67-436f-bc70-60db49b2918fn%40googlegroups.com.

[dspace-tech] Re: 7.6.1 ORCID authentification fail

[Andrew K]

UPD: ORCID authentification still fails in some browsers like older Chrome 
109 (Win7).

пʼятницю, 1 березня 2024 р. о 00:34:51 UTC+2 Andrew K пише:

UPD: It's the same issue https://github.com/DSpace/DSpace/issues/9109
Moving 
*plugin.sequence.org.dspace.authenticate.AuthenticationMethod = 
org.dspace.authenticate.PasswordAuthentication*
before 
*plugin.sequence.org.dspace.authenticate.AuthenticationMethod = 
org.dspace.authenticate.OrcidAuthentication*
fixed the ORCID authentification.

Also, ORCID login button moved down where it was before. Great

-- 
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/a4d3bbd8-4f47-48cf-9304-686e8525b8d5n%40googlegroups.com.

[dspace-tech] 7.6.1 ORCID authentification fail

[Andrew K]

Hello!

I moved from 7.6 server to a 7.6.1 server.
Looks like every possible setting is made.
But ORCID authentification fails (worked in 7.6).
[image: 2024-02-29_235704.png]

Nothing special in the logs.
What else do I miss?

UPD: That looks like a seriuos bug: after a failed ORCID login I enter 
admin credentials, press Login and... I'm logged with the ORCID profile, 
not admin!

Thanks,
Andrew

-- 
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/1cd8a8b2-1d32-4a05-8644-85a2e2944970n%40googlegroups.com.

[dspace-tech] Re: 7.6.1 ORCID authentification fail

[Andrew K]

UPD: It's the same issue https://github.com/DSpace/DSpace/issues/9109
Moving 
*plugin.sequence.org.dspace.authenticate.AuthenticationMethod = 
org.dspace.authenticate.PasswordAuthentication*
before 
*plugin.sequence.org.dspace.authenticate.AuthenticationMethod = 
org.dspace.authenticate.OrcidAuthentication*
fixed the ORCID authentification.

Also, ORCID login button moved down where it was before. Great

пʼятницю, 1 березня 2024 р. о 00:21:19 UTC+2 Andrew K пише:

> Hello!
>
> I moved from 7.6 server to a 7.6.1 server.
> Looks like every possible setting is made.
> But ORCID authentification fails (worked in 7.6).
> [image: 2024-02-29_235704.png]
>
> Nothing special in the logs.
> What else do I miss?
>
> UPD: That looks like a seriuos bug: after a failed ORCID login I enter 
> admin credentials, press Login and... I'm logged with the ORCID profile, 
> not admin!
>
> Thanks,
> Andrew
>

-- 
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/974c2502-9067-49c9-93b7-d47da7fd7595n%40googlegroups.com.

[dspace-tech] Re: Item Counters for Communities and Collections not working well

[Andrew K]

Hi Caty,

It depends on how you define "working well". I just don't expect immediate 
updates. Not sure how long it takes, but AFAIK the next day the numbers 
look good. That's well enough for me )

WBR,
Andrew

понеділок, 26 лютого 2024 р. о 15:06:06 UTC+2 Caty пише:

> Hi, Is anyone using item counters for Communities and Collections? Are 
> they working well?
>
> Thank you,
> Caty
>
> Pe sâmbătă, 17 februarie 2024, la 17:10:55 UTC+2, Caty a scris:
>
>> Hi,
>>
>> The setting:
>> webui.strengths.show = true
>> is not updating the item counter for collections and communitiesin DSpace 
>> 7.6/DSpace 7.6.1.
>> Not even dspace index-discovery -b is not updating the item counters.
>> Only tomcat restart in updating the counters.
>>
>> Seetting webui.strengths.cache to false failes DSpace to load collections 
>> and communities
>>
>> The same is on demo dspace:
>> The collection collection1_test 
>>  
>> in 
>> this community
>>  https://demo.dspace.org/communities/dd23e4d3-92fa-460f-a6a9-b612fef7aa79
>> has 1 item , but displays counter 0:
>> collection1_test 
>>  
>> (0 
>> )
>>
>> It is not updated in real time, not even hours after adding the item.
>>
>> In DSpace 6 it was working very well, the counter was updated within 
>> seconds after adding items.
>>
>> So the behaviour of item counters is as described here:
>> https://github.com/DSpace/dspace-angular/issues/1787 
>> *
>> mpasternak commented 2 weeks ago
>> That was the first thing I thought about. I ran dspace index-discovery 
>> -b, then re-loaded Solr core but it did not help. The numbers still don't 
>> add up.
>>
>> @mpasternak
>> mpasternak commented 2 weeks ago
>> Also, enabling web.strengths.cache to false causes collections to freak 
>> out. What logs should I examine? Not much in dspace logs, not much in 
>> Catalina.out 
>> ***
>>
>> We really need this feature..
>> Could you give a solution, please?
>> Thank you very much,
>> Caty
>>
>

-- 
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/d2c7447b-3f8b-41b7-9e26-e0bbe3cf10b0n%40googlegroups.com.