Re: Add metadata in oai/transformer

[DSpace Community]

Hi Santiago,

Please do not set the value of `dspace.entity.type` to the same value as `dc.type`.  The `dspace.entity.type` metadata field is used to determine the type of Configurable Entity, see docs at https://wiki.lyrasis.org/display/DSDOC7x/Configurable+Entities

That field is an internal, DSpace-managed field (as are all fields in the "dspace" metadata schema).  If you set that "dspace.entity.type" field to an unexpected value, there may be a chance you could cause odd behaviors in your DSpace site.

To answer your question as well. There is currently not a way to copy one field value into another automatically.  That's not possible at this time without custom code.

Tim

On Wednesday, May 10, 2023 at 7:43:43 AM UTC-5 santilo...@gmail.com wrote:

Sorry, the subject is wrong, I was referring to another question I had. Please don't take it into account.

On Wednesday, May 10, 2023 at 2:19:47 PM UTC+2 Santiago Lo Coco wrote:

Hello,

I am writing to ask about how to add a new metadata field after creating a new item in DSpace (with submission-forms.xml). Specifically, I am interested in adding the metadata field "dspace.entity.type" and setting it to the same value as the "dc.type" field.

I was thinking of adding a hidden element in the submission-forms.xml that depends on the other field but I don't know if that is possible.

Regards,

Santiago.

[DSpace Community]

Hi Santiago,

Yes, of course, you can use "dspace.entity.type" for configuring your own Entity Model as described in https://wiki.lyrasis.org/display/DSDOC7x/Configurable+Entities

However, I was pointing out that "dc.type" is a completely different field with different values (by default) in DSpace.  If you attempt to sync all the values of "dc.type" into your "dspace.entity.type" that may result in odd behaviors. For example, if you change dc.type & sync it to "dspace.entity.type" it may *change the type of Entity* dynamically in your submission form.  This can result in odd behaviors because there are different submission forms per Entity type & there's no way to reload the correct Entity Type form dynamically if the value of "dspace.entity.type" changes.  

For instance, if "dspace.entity.type" starts out as "Publication", and then dynamically changes into "Person", then you'd remain on the Submission form for a Publication but the underlying object would now be a Person Entity.  This is the problem with changing the value of "dspace.entity.type" during a submission.

Basically, you are welcome to use "dspace.entity.type" as documented... but allowing it to be changed on the submission form may result in odd behaviors or errors.

Tim

On Wednesday, May 10, 2023 at 1:50:30 PM UTC-5 santilo...@gmail.com wrote:

Thanks for your response, Tim.

About setting the value of `dspace.entitity.type`: Isn't it correct to configure my own entity model? I created new types in `relationship-types.xml` and then run the script to `initialize-entities`.

I really used them for discovery/search and it seems to work perfectly (2+ months running).

Regards,

Santiago.