[dspace-tech] Re: initialize entities

[Andrii Drevych]

How did you solve the problem?

вівторок, 3 жовтня 2023 р. о 14:41:42 UTC+3 Alex B пише:

> the issue is resolved!
>
> пятница, 29 сентября 2023 г. в 12:48:33 UTC+3, Alex B: 
>
>> Dear Colleagues, I installed version Dspace 7.6 / UI 7.6.
>> ran the command /dspace/bin/dspace initialize-entities -f 
>> /dspace/config/entities/relationship-types.xml
>> uncommented the option
>> researcher-profile.entity-type = Person
>> in researcher-profile.cfg
>> uncommented the option
>> choices.plugin.dspace.object.owner = EPersonAuthority
>> choices.presentation.dspace.object.owner = suggest
>> authority.controlled.dspace.object.owner = true
>> in authority.cfg
>>
>> But the option to create an entity item did not start (see 2023-09-29 
>> 12-36-08)
>> in version 7.4 this option worked (see Screenshot from 2023-09-29 
>> 12-39-31 )
>>
>> how to enable the item ?
>>
>> 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/d27e2776-21eb-4823-be63-d071836ea840n%40googlegroups.com.

[dspace-tech] DSpace 6.3 to 7.6 Migration: Solr Core Migration Questions

[Carolyn Sullivan]

Hello all,

We're migrating from DSpace 6.3 to DSpace 7.6.  With regard to the Solr 
cores, we're wondering... what are the OAI and Search cores, and should we 
migrate those?  Did other folks here migrate them during their migrations?

Additionally: We're not sure what to do with our legacy statistics from 
pre-2014 since they don't have uuids.  Is there any way to import them into 
7.6?  What are other people doing with theirs?

Thank you so much for your help, and any information would be greatly 
appreciated :)
Best,
Carolyn.

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

[dspace-tech] Re: 500 Service Unavailable

[DSpace Technical Support]

Hi,

A 500 error is usually a sign of a communication issue between the frontend 
and backend.  This is one of the Common Installation Issues listed at the 
bottom of the Install Guide 
at 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-%22500ServiceUnavailable%22fromtheUserInterface

If the instructions there do not help, you should look for additional 
information about the cause of the 500 error by using our troubleshooting 
guide.  The root cause will be an error message in either the User 
Interface (visible in your Browser's DevTools) or in the backend (visible 
in the 
logs). 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

On Tuesday, February 13, 2024 at 6:58:05 AM UTC-6 chakkara...@gmail.com 
wrote:

> Dear Sir / Madam,
> I have installed Dspace7.6.1  on Windows Server,  however when i try to 
> launch i get the error: "500 Service Unavailable. The server is temporarily 
> unable to service your request due to maintenance downtime or capacity 
> problems. Please try again later. "  Can somebody help to resolve it. Will 
> be grateful.
>

-- 
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/7d40ced4-6e96-48f2-82f4-bbaf639eddf2n%40googlegroups.com.

Re: [dspace-tech] Re: Access control -> Groups stuck "Loading"

[DSpace Technical Support]

Hi Alex,

I did see that you mentioned narrowing down to the "Anonymous" group.  
However, that explanation didn't make sense to me based on the error you 
shared (it's possible you have more errors though that show the Anonymous 
group being impacted).  The error you shared seems to imply there **is** a 
ResourcePolicy issue, but it's related to a Group of the name  
 "COLLECTION_[id]_ITEM_DEFAULT_READ" which cannot map to a Collection.  
 It's possible I'm also misreading things though...(I'm not an expert in 
every line of code in DSpace)

In general though, I *agree* that there's something fishy going on with 
your ResourcePolicies.  This sounds somewhat related to this other bug 
report from November: https://github.com/DSpace/DSpace/issues/9190  ... 
though that ticket is about resource policies with *null* EPerson/Group, 
and not a null Object.   There *is* a possible fix in the works for that 
issue here: https://github.com/DSpace/DSpace/pull/9191  It's still under 
review though and I'm not sure if it's the same issue you see, but it's 
semi-related.

Overall, you are correct that a ResourcePolicy should point to an 
*object*.   It sounds like somewhere along the way, some messy data made 
it's way into your ResourcePolicy table.   You could try deleting some of 
those seemingly invalid rows in that table... but before doing so, I'd 
recommend ensuring you have a backup (so you can revert those deletions if 
you delete too much).

However, I'll also warn that it's *possible* some of your data didn't 
upgrade/migrate properly.  So, if you are seeing major issues elsewhere in 
the application (accessing objects, logging in, performing other actions), 
then that could be a sign the migration didn't work properly.  If not, then 
it could just be some bad data in that ResourcePolicy table.

That's my best advice for now.  Good luck!

Tim


On Monday, February 12, 2024 at 2:08:24 PM UTC-6 Alex Fraser (Staff) wrote:

> Hi Tim,
>
>  
>
> Thanks for the reply. The data migration was (intended to be) the process 
> you linked to, migration to a new server. Both old and new use PostgreSQL 
> on RHEL. For the database, I created an empty one, created the pgcrypto 
> extension, populated the database with output from pg_dump on the current 
> server, and then ran “dspace database migrate ignored” prior to starting 
> Tomcat. I didn’t notice any problem with the database dump/import (not to 
> discount the possibility I missed it).
>
>  
>
> I can’t tell if it’s just my lack of understanding or if you missed where 
> I wrote that I isolated the problem to the Anonymous group specifically (in 
> fact that seems to be the only one triggering the error described). I’m not 
> sure if I’ve followed the code correctly, which led me to suspect 
> resourcepolicy data, so I may be way off, but I observe:
>
>  
>
> select count(*) from resourcepolicy where epersongroup_id = (select uuid 
> from epersongroup where eperson_group_id = 0) and action_id = 10 /* 
> Constants.DEFAULT_ITEM_READ */ and resource_type_id = 3 /* 
> Constants.COLLECTION */ and dspace_object is null;
>
> count
>
> ---
>
> 33
>
>  
>
> And it looks to me like this is an inconsistency in the 5.6 database 
> propagated, probably as intended, through migrations (similar to the other 
> thread I started, https://groups.google.com/g/dspace-tech/c/K-YWS0GpRmk), 
> eg:
>
>  
>
> select count(*) from resourcepolicy rp where rp.epersongroup_id = 0 and 
> rp.action_id = 10 and rp.resource_type_id = 3 and not exists(select * from 
> collection where collection_id = rp.resource_id);
>
> count
>
> ---
>
> 33
>
>  
>
> More generally, back in the 7.6.1 database:
>
>  
>
> select resource_type_id, count(*) from resourcepolicy where dspace_object 
> is null group by resource_type_id;
>
> resource_type_id | count
>
> --+---
>
> 6 | 2
>
> 3 |   254
>
>  
>
> As these represent only a tiny fraction of the ~400k resourcepolicy rows 
> I’m guessing there should be none. If so, the question of course is how 
> best to reach that state, but in any case there is still a problem 
> somewhere, so any further suggestions would be great.
>
>  
>
> Kind regards,
>
> Alex
>
>  
>
> *From:* DSpace Technical Support  
> *Sent:* 09 February 2024 17:26
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Re: Access control -> Groups stuck "Loading"
>
>  
>
> Hi Alex,
>
>  
>
> Here's where that error occurs: 
> https://github.com/DSpace/DSpace/blob/dspace-7.6.1/dspace-api/src/main/java/org/dspace/content/CollectionServiceImpl.java#L938-L941
>  
> and it's called from here: 
> https://github.com/DSpace/DSpace/blob/dspace-7.6.1/dspace-api/src/main/java/org/dspace/eperson/GroupServiceImpl.java#L806
>
>  
>
> The error appears to be saying that DSpace has found a group named 
> "COLLECTION_[id]_ITEM_DEFAULT_READ" which does NOT seem to match with a 
> corresponding Collection?  I.e. the "id" doesn't match the 

Re: [dspace-tech] MetadataValue: latestForDiscovery

['Eike Martin Löhden' via DSpace Technical Support]

Hej,

as far as I can oversee it, the problem is, that there is no 
metadatafield "relation.isPersonOfJob". You have to add the metadata 
fields "relation.isPersonOfJob.latestForDiscovery", 
"relation.isPersonOfJob", "relation.isJobOfPerson.latestForDiscovery" 
and "relation.isJobOfPerson" into your metadata registry 
[dspace-instance]/config/registries/relationship-formats.xml. Then you 
can load the updated registry via command line ("dspace registry-loader 
-metadata ") and it hopefully works...


Kind regards,
Eike.

Am 13.02.24 um 13:39 schrieb Aly Badr:


Hello,

I tried to add a new entity called "Job" and link it with the existing 
entity "Person". While everything is working smoothly, there's a 
glitch in the submission form where the chosen "Job" doesn't show up 
properly. There's also an error in the log, but without more details, 
it's hard to pinpoint the exact problem.


Since the relation "isJobOfPerson" is set up correctly in the relevant 
files "relationship-types.xml", 
"discovery.xml","virtual-metadata.xml", "submission-forms.xml" what 
else need to be checked to correct this problem?


Certainly, the initialization of entities has been executed, and 
reindexing, as well as server restarts, have been performed as part of 
troubleshooting


Thanks,
Aly
 virtual-metadata.xml 

    


    
        
            dc.title
        
    
    
    

 virtual-metadata.xml 


ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A 
MetadataValue was attempted to construct with MetadataField for 
parameters: metadataschema: relation, metadataelement: isJobOfPerson, 
metadataqualifier: null


ERROR:  org.dspace.content.RelationshipMetadataServiceImpl @ A 
MetadataValue was attempted to construct with MetadataField for 
parameters: metadataschema: relation, metadataelement: isJobOfPerson, 
metadataqualifier: latestForDiscovery


ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A 
MetadataValue was attempted to construct with MetadataField for 
parameters: metadataschema: relation, metadataelement: isPersonOfJob, 
metadataqualifier: latestForDiscovery


ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A 
MetadataValue was attempted to construct with MetadataField for 
parameters: metadataschema: relation, metadataelement: isJobOfPerson, 
metadataqualifier: null


ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A 
MetadataValue was attempted to construct with MetadataField for 
parameters: metadataschema: relation, metadataelement: isPersonOfJob, 
metadataqualifier: null

--
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/6e2c2970-1da0-4152-b07c-5e8203331869n%40googlegroups.com 
.


--
Eike Martin Löhden
Projektmitarbeiter, DFG-Projekt mediarep, Infrastruktur Digitale Sammlungen
Philipps-Universität Marburg
Deutschhausstraße 9
35032 Marburg

+49 6421 28-25238
eike.loeh...@staff.uni-marburg.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/38c7b7eb-e796-4a31-b6c8-ba8a4b2566e1%40staff.uni-marburg.de.


smime.p7s
Description: Kryptografische S/MIME-Signatur

[dspace-tech] MetadataValue: latestForDiscovery

[Aly Badr]

Hello,

I tried to add a new entity called "Job" and link it with the existing 
entity "Person". While everything is working smoothly, there's a glitch in 
the submission form where the chosen "Job" doesn't show up properly. 
There's also an error in the log, but without more details, it's hard to 
pinpoint the exact problem.

Since the relation "isJobOfPerson" is set up correctly in the relevant 
files "relationship-types.xml", "discovery.xml","virtual-metadata.xml", 
"submission-forms.xml" what else need to be checked to correct this problem?

Certainly, the initialization of entities has been executed, and 
reindexing, as well as server restarts, have been performed as part of 
troubleshooting

Thanks,
Aly
 virtual-metadata.xml 






dc.title





 virtual-metadata.xml 


ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A MetadataValue 
was attempted to construct with MetadataField for parameters: 
metadataschema: relation, metadataelement: isJobOfPerson, 
metadataqualifier: null

ERROR:  org.dspace.content.RelationshipMetadataServiceImpl @ A 
MetadataValue was attempted to construct with MetadataField for parameters: 
metadataschema: relation, metadataelement: isJobOfPerson, 
metadataqualifier: latestForDiscovery

ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A MetadataValue 
was attempted to construct with MetadataField for parameters: 
metadataschema: relation, metadataelement: isPersonOfJob, 
metadataqualifier: latestForDiscovery

ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A MetadataValue 
was attempted to construct with MetadataField for parameters: 
metadataschema: relation, metadataelement: isJobOfPerson, 
metadataqualifier: null

ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A MetadataValue 
was attempted to construct with MetadataField for parameters: 
metadataschema: relation, metadataelement: isPersonOfJob, 
metadataqualifier: null

-- 
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/6e2c2970-1da0-4152-b07c-5e8203331869n%40googlegroups.com.

[dspace-tech] 500 Service Unavailable

[chakkaravarthy kp]

Dear Sir / Madam,
I have installed Dspace7.6.1  on Windows Server,  however when i try to 
launch i get the error: "500 Service Unavailable. The server is temporarily 
unable to service your request due to maintenance downtime or capacity 
problems. Please try again later. "  Can somebody help to resolve it. Will 
be grateful.

-- 
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/57a44717-6f24-4a62-9973-bd3e4137b6d5n%40googlegroups.com.