Enable grouping of metadata (schema) documents.

[VolkerHartmann]

Multiple tags per Digital Object would allow to group/filter them.
Alternatively, this could also be enabled via Collections as the managing instance.

[VolkerHartmann]

You can also do both.
The base repo also supports tags.

[sabrineChe]

I think using collections is a good idea. Let's wait and see the detailed NFFA requirements.
Otherwise, concerning the multiple tags per DO, is it supported by the metastore or is it just supported by the base repo?

[VolkerHartmann]

I think using collections is a good idea. Let's wait and see the detailed NFFA requirements.
Otherwise, concerning the multiple tags per DO, is it supported by the metastore or is it just supported by the base repo?

It's not supported by the metastore right now. But it could be implemented (easily).

[ThomasJejkal]

I would strongly recommend not using tags for this purpose. The idea behind tags is to mark specific resources, e.g., for realizing favorites or things like that. Using them for structuring has the strong disadvantage, that the structure can only be created on the client side and results cannot be ordered by tags. Thus, listing one page results in a structure, where the second page might modify the structure due to new tags.
Instead, I would really recommend to use the Collection Registry following the principle "eat your own dog food" because the Collection Registry was made exactly for that purpose...to build up hierarchical aggregations of resources which do not support this be design.

[ThomasJejkal]

Isn't this solved in the meantime by the MetaStore page of the frontend-collection ?

[Pfeil]

As I am assigned: Does it affect FAIR DOs or the Typed PID Maker in any way? I think we had some tagging possiblities in PIDs, but I'd have to look up the details. Asking because I am cleaning my assigned-issues-list. ;)