Limitation of the nested forms

[Gary Hsu]

Dear all, 

does anyone know whether the new feature "nested metadata" in DSpace 10 only supports dc (dublin core) schema for the parent form? 

In the documentation, the suggested format is

<form name="publicationStepGroup">  (parent)

<form name="publicationStepGroup-dc-contributor-author"> (child)

I got this error when using my own schema: 

ERROR TypeError: Cannot read properties of undefined (reading 'securityLevel')
at DsDynamicRelationInlineGroupComponent.getRowValue (
)
at DsDynamicRelationInlineGroupComponent.onChange (
)
at DsDynamicRelationInlineGroupComponent_Conditional_1_Template_ds_form_dfChange_0_listener (
)
at executeListenerWithErrorHandling (
)
at Object.wrapListenerIn_markDirtyAndPreventDefault [as next] (
)
at ConsumerObserver.next (
)
at SafeSubscriber._next (
)
at SafeSubscriber.next (
)
at

at errorContext (
)

Thanks for your help in advance

Gary

[DSpace Technical Support]

Hi Gary,

As far as I can tell, the nested metadata feature should be able to support other metadata schema, as long as the schema, element, and qualifier are defined. The example given in the documentation for a non Dublin Core schema is within a child form, but it should be the same format within the parent form:

<dc-schema>oairecerif</dc-schema>

<dc-element>author</dc-element>

<dc-qualifier>affiliation</dc-qualifier>

However, I haven't tested it myself and that could be incorrect, so if anyone more familiar with the feature knows otherwise please let us know. 

Either way, it would be best to determine if the error you're encountering is due to the schema or something unrelated.  What was the full configuration you added to submission-forms.xml that resulted in this error? Also to confirm, the nested metadata feature did work as expected with a Dublin Core parent field?

Last, the error indicates something going wrong with "securityLevel" which is related to the Metadata Security Configuration feature also added as part of 10.0. Not sure how, but I'd also recommend checking that documentation in case there's something going on with the interaction between those two features. 

Hope that's a start. Best,

-Lia

[Gary Hsu]

Hi Lia,

I figured it out how to do it correctly.

The item in the parent form has to be identical to the first item in the child form. 

For example,  the red items in both forms have to be exactly the same in terms of its schema name (dc), element (contributor), and qualifier (editor). The child should be also named accordingly (dc-contributor-editor).

The second item (green) in the child form can be any other schema you prefer.  The logic sounds werid but that is how I get it work. 

<form name="publicationStepGroup">   (parent form)
    <row>
        <field>
            <dc-schema>dc</dc-schema>
            <dc-element>contributor</dc-element>
            <dc-qualifier>editor</dc-qualifier>
            <repeatable>false</repeatable>
            <label>Editor</label>
            <input-type>inline-group</input-type>
            <hint>The editors of this publication.</hint>
            <required>You must enter at least the author.</required>
        </field>
    </row>
</form>

<form name="publicationStepGroup-dc-contributor-editor">   (child form)

          <row>
            <field>
              <dc-schema>dc</dc-schema>
              <dc-element>contributor</dc-element>
              <dc-qualifier>editor</dc-qualifier>
              <label>Editor</label>
              <input-type>onebox</input-type>
              <repeatable>false</repeatable>
              <required>You must enter at least the author.</required>
              <hint>The editors of this publication.</hint>
            </field>
            <field>
              <dc-schema>oairecerif</dc-schema>
              <dc-element>editor</dc-element>
              <dc-qualifier>affiliation</dc-qualifier>
              <label>Affiliation</label>
              <input-type>onebox</input-type>
              <repeatable>false</repeatable>
              <required />
              <hint>Enter the affiliation of the editor as stated on the publication.</hint>
            </field>
          </row>
</form>

Kind regards,

Gary