Multiple occurrences in a Metadata field

[Richard van 't Riet]

Hi all,

I have a question about metadata configuration ; We have a client for which we are upgrading their RS and they have a request for a metadata field to hold multiple 'occurrences' (values). which in itself is a kind of 'relational' database aspect.

If these values were just a simple word I would probably default this to a Tag field, but in this case these need to hold multiple words, like a short sentence.

This makes me feel that a tag field is not the best solution.

Does anyone come across this before and maybe hav a suggestion ?

many thanks for any feedback ! Richard

[Trond Helge Rolland]

Hi Richard, my suggestion would be to first ask your client for what kind of values they want to store. If we're talking alphanumeric you can probably use a comma separated string, so "random,word,here" and then use an API call to fetch the field and then split it by the delimiter of your choice. 

Do the values come from another system automatically, are they stored by the user when uploading / editing the resource, are they informative for the user in RS or more a "backend" connection value etc, there are probably a lot of different ways to solve it, but it all depends on what kind of behaviour your client wants/expects. 

(I believe it's often called an XY problem, where the client asks for X because they believe that will give them Y)