Andrew,
Your question is a good one. I will respond to what I can and hope that others will join in to add more detail and correct me where I am wrong.
Metalnx was an open source project started at EMC (now Dell EMC) to help people who wanted to more easily administer and work with iRODS via a GUI. The goal was to create a UI that will make it easier for an average user and administrator to interact with IRODS and not need strong Linux nor programming skills to interact with the framework successfully.
Metalnx is one of several IRODS GUIs that have been created over time. They all have different advantages. EMC put Metalnx into open source in hopes that a user community will form over time to enhance and bring the tool forward for the common good. Earlier this spring the source base (V1.4) was contributed to the iRODS consortia and there are several people working on enhancements on the V2.0 branch you will find in
github.com/irods-contrib/metalnx-web.
In most respects, the Cloud Browser and Metalnx are very similar.
Metalnx advantages:
- Supports many iRODS system administration tasks (user, group creation/modification, permissions, storage grid layout, iRODS grid monitoring)
- Supports user rule deployment across the nodes in an iRODS grid (this is in V1.4)
- Allows users to give access to others via links (not tickets) to allow movement in the collection tree around blocked path permissions
- Uses Thymleaf to allow page creation on the Metalnx server so to lower the compute overhead on thin clients and provide scalability
- A version of metadata templates (public / private) which can be run over individual or collections of objects in a collection.
- Some auto extraction of metadata tags (this is not a Metalnx feature, the code was written to invoke a metadata rule on ingest based on the file suffix if a rule is in the rule base). I believe the latest version of the Cloud Browser does similarly.
There is work underway by members of the Metalnx Community to bring into Metalnx some of the best elements of the Cloud Browser along
with enhanced support for metadata templates.
Cloud Browser advantages:
- WebDav support (Metalnx does not support this)
- CSS customizations to support organizational look and feel
- Personalized collection views
- Basic metadata templates based on the metadata template model the metadata working group is adopting.
Both do important things like:
- support tickets
- allow searching for Metadata tags
- PAM support for authentication
- Collection browsing
- Object permissions, versioning, and metadata tag viewing
- Metadata tag searching
You asked if the UI will make it easier to ingest metadata. That depends on how the evolution of Metalnx and the cloud browser goes. The original Metalnx team started some work in the UI to build a sophisticated metadata template engine running through the UI. IRODS and its rule engine is a fast/powerful tool. The work underway in the Metadata working group is moving towards automated metadata extraction being done by iRODS rules and microservices and using the iRODS framework to feed information about metadata templates to the GUI (for data consistency) keeping all this information in the ICAT for consistency. I am not the best person to speak on the details of this.
At the other end will be easier searching and matching. Metalnx does metadata searching through a simple interface which lets one build a search term based on metadata tags (or wildcards), matching criteria (equal, not equal, contains, does not contain), and metadata fields (value, units) along with object property data (TLM, size, etc.). The structure for this was based on feedback from a number of genome researchers we interviewed. I am sure the interface can and will be improved over time, especially after more work is done integrating IRODS with strong search engines. I know the Cloud Browser supports metadata search via the UI, but I have not used it in some time so my knowledge is old.
Hopefully, this helps answer some of your questions.