NB: Blanks in the tables below indicate missing information Please help out by providing missing information / fill out the blanks!
First of all, for a general overview, here is an an overview of modules in the DINA-Web system along with information about contributing teams. Please use this link if you are not familiar with the various components that together make up the DINA-Web system.
The tables below provide an overview in terms of progress and maturity across these contributed components. Suggestions have been raised in the DINA Technical Committee to test components for Accessibility using certain tools and also for Security using other tools. Results from such tests are not yet availabe but could complement the tables below once made available.
The table below lists various DINA-Web components (both Web APIs, Web UIs and CLI tools) and their status in terms of whether there is publicly accessible documentation, whether the source code is available at GitHub or BitBucket or otherwise openly accessible, whether the component uses continuous integration so that builds are reproducible and whether there are tests being run.
The stakeholder column indicates the primary user group for the module. The value “Client” indicates that an app such as a web client or even a client library is the intended primary user of the module, so the REST APIs will provide machine readable data to such client. We use “wrangler” for users that work with data migration, such as database administrators and power users. We use “curators” for the end users, often biologists, that work with collection management using web based user interfaces. We use “DevOps” to indicate users that are developing and running the DINA-Web system. Sometimes stakeholder groups overlap.