[FEATURE] Add information to collection/data object browser table

[ll4strw]

Is your feature request related to a problem? Please describe.

Yoda v1.9.0
The collection/data object browser table presents limited information

Would it be possible to make this table customisable and let a user add/remove columns from the view?
Useful information to be visualised would be:

• owner
• ACLs
• number of replicas
• collection/data object metadata

[stsnel]

Thank you for the proposal. We will ask input from our other stakeholders regarding whether they support this proposed change, and what priority it should have relative to other feature requests. I expect we've received their reactions by the end of October.

[stsnel]

The outcome of the stakeholder meeting was that there is a wider need to be able to view / work with collection and data object metadata in the portal. We intend to explore how we can best design functionality in a way that it supports as many use cases as possible.

@ll4strw If you have additional information that you're able to share about your use case(s) for working with metadata in the portal , can you please add it to the ticket, so that we can take it into account?

At this moment, we don't plan to add owner or ACL information in the research module, since we use the group manager to let users manage permissions on a group-level (rather than at a collection or data object level). This could change if the Yoda permission model changes in the future. We also don't have wider support to prioritize displaying replica information in the research module, at the moment.

[ll4strw]

@stsnel My main concern at the moment is possible integrations with other systems (e.g. electronic lab notebooks, dangerous substance registration systems, microscopy images repositories, etc...). If I imagine integration occurring at the iRODS level through metadata exchange, then YoDa users should be able to view/edit/search data objects/collections metadata. Pre-population of these metadata, as suggested in #471, is indeed an important feature if I think of those scientific data formats which carry metadata with them (HDF5, FITS, etc...).
In the future I am also expecting data objects metadata to play an important role in data deduplication, ownership attributions, etc...differently than traditional checksums techniques. So I am thinking about how to make YoDa ISCC (International Standard Content Code) aware. ISCC is a new ISO standard for digital content identification which is metadata aware. Here are a few interesting links

• https://iscc.io/
• https://github.com/iscc
• https://github.com/ll4strw/python-irodsclient-iscc