plazi / lycophron

Batch uploader to Zenodo
Creative Commons Zero v1.0 Universal
2 stars 5 forks source link

Coping with UPDATE of custom metadata fields with multiple values/entries #3

Closed mguidoti closed 2 years ago

mguidoti commented 3 years ago

Hi Alex,

We recently discussed, by email, on how update custom metadata fields and that raised me a couple of question, especially because we're designing this tool to be universally used - not exclusively used by our domain.

Take our universe of custom metadata fields as an example. We have some fields that will always have a single value (most of the DwC based ones) and some other that will have multiple values, like, locations in treatments, or, the OBO ones. For the ones with unique values, the idea of using a relational database (like a spreadsheet to an extant) as input would work perfectly fine. We can take the value on that specific column/row and replace it in the server. But if you start thinking about the custom metadata fields with multiple values, we need to know the value to be changed, not only the new value. Then I have the following questions:

  1. how should the user input the data in the incoming spreadsheet if we need the current state and the new desired state?
  2. how can we tell Lycophron which fields require the two values, as this will be used universally?
  3. are spreadsheets still the best input now that we consider this case?

I've some ideas in mind, but I'll let you start the brainstorm here.

Thanks!