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

<util:map id="isJobOfPersonMap">
    <entry key="person.jobTitle" value-ref="personJob_other"/>
</util:map>
<bean class="org.dspace.content.virtual.Collected" id="personJob_other">
    <property name="fields">
        <util:list>
            <value>dc.title</value>
        </util:list>
    </property>
    <property name="useForPlace" value="true"/>
    <property name="populateWithNameVariant" value="true"/>
</bean>

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

[Eike Martin Löhden]

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 <file-path>") and it hopefully works...

Kind regards,
Eike.

Am 13.02.24 um 13:39 schrieb Aly Badr:

--
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/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.l...@staff.uni-marburg.de

[BADR Aly Aboubakr]

Thank you, Eike, for your response,

 

Running "registry-loader -metadata "fixed the error message in the log file; however, it did not resolve the display issue in the workspace item (submission form). I suspect that another file needs to be modified for this to work.

 

Best regards,

Aly

You received this message because you are subscribed to a topic in the Google Groups "DSpace Technical Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dspace-tech/Gjv6xPYJ95U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dspace-tech...@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.

[Ghousson]

Hello,

we have the same problem with the invisible entity in the submission form in DSpace 7.6. Did you find a solution in the configuration? 

Thanks in advance and best regards

Dana

ZHAW Zürcher Hochschule für Angewandte Wissenschaften
Hochschulbibliothek Winterthur
Dana Ghousson
Applikationsentwicklung
Turbinenstrasse 2
Postfach
CH-8401 Winterthur

danarim....@zhaw.ch

www.zhaw.ch/openaccess
https://digitalcollection.zhaw.ch

[Ghousson]

Hello Aly

We found a solution for our "invisible" entity in the submission. To make them appear they need a Component "{EntityName}ItemMetadataListElement" in the frontend. Maybe this helps you too. I came across the solution on new project metadata representation component by paulo-graca · Pull Request #2277 · DSpace/dspace-angular · GitHub

Best regards

Dana