Hi, I've checked the metadata and it's loaded properly. Maybe I wasn't clear, but the metadata appears just fine in after you select the document type and click next. So I believe that the metadata fields are not the issue. The problem appears when the second page (the one with the specific metadata values for that doc type) is refreshed, whether it's done manually by the user or automatically by the system when for example an "add" button is clicked.
Thanks for answering, Agustín El jueves, 12 de mayo de 2022 a la(s) 23:05:41 UTC-3, euler escribió: > Hi, > > I've encountered this also. Make sure that all the metadata fields in your > input-forms.xml actually exist in the metadata registry. In your example, > by default, there is a dc.contributor field in the metadata registry but > perhaps other metadata fields in your input forms are not yet defined in > the metadata registry hence the error when a submitter tried to continue on > the next page. > > Hope this helps. Regard, > euler > > On Thursday, May 12, 2022 at 11:14:30 PM UTC+8 [email protected] > wrote: > >> Hi, I need to use the type-bind feature to request my users to complete >> specific metadata for each document type. Since i want to be able to have >> different types of documents in the same collection, this is the solution >> that works best for me. >> >> *The configuration i've tried is like this:* >> The user is in a collection and starts a submission, when they arrive to >> the *Description Step* the *first page of the input form* asks them to >> select the document type. Then, in the *second page of the input form*, >> they are shown only the metadata that applies to that specific document >> type. >> I've tried to achieve this by modifying the *input-forms.xml* file to >> have the following lines: >> >> <form-definitions> >> >> <form name="traditional"> >> <page number="1"> >> <field> >> <dc-schema>dc</dc-schema> >> <dc-element>type</dc-element> >> <dc-qualifier></dc-qualifier> >> <repeatable>false</repeatable> >> <label>File type</label> >> <input-type value-pairs-name="common_types">dropdown</input-type> >> <hint>File type</hint> >> <required></required> >> </field> >> </page> >> >> !<-- And then, for example, a metadata only available for the "thesis" >> type --> >> >> <page number="2"> >> <field> >> <dc-schema>dc</dc-schema> >> <dc-element>contributor</dc-element> >> <dc-qualifier></dc-qualifier> >> <repeatable>true</repeatable> >> <label>Thesis director</label> >> <input-type>name</input-type> >> <hint></hint> >> <required></required> >> <type-bind>Thesis</type-bind> >> </field> >> </page> >> >> ------------------------------------------------------------------------ >> >> This works but the *problem* is that when the user reloads the second >> page or it's done automatically (for example, when clicking the "add" >> button) the page becomes blank. I believe this is because Dspace fails to >> remember the Doc Type and so no type-bind metadata is shown. >> >> *Failed solution:* >> I've tried to fix this by having the type metadata and the rest of the >> metadata in the same page. But in this case if the user doesn't mannually >> reloads the page, the type-bind metadata is not shown. Also, it gives the >> user the ability to fill the metadata specific to a thesis for example and >> then change the Doc type. >> >> *What can I do to fix this? Is there a better solution to my problem?* >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/afea49c6-3157-4857-89c6-1f28b1323065n%40googlegroups.com.
