BrandonMrBot
commented
1 month ago Incorporating Enketo for completing metadata forms for ClimMob projects requires developing endpoints and interfaces tailored to handle the metadata functionality. Several considerations must be addressed to achieve this:
- Open access to forms:
The forms must be accessible without requiring a username and password, unlike the typical Enketo setup, where authentication is usually necessary.
- Limitations with project definition in ODK form:
It is not possible to use the predefined information in the project definition within the ODK form as it is generic for all projects and no default values can be set (e.g. auto-completion of the “project name” field).
- Metadata modification:
Once metadata is submitted to ClimMob from Enketo, editing the data is not possible. The only solution is to manage data updates through ClimMob's interface or start a new form to replace the existing record.
- Standardization for analysis:
The metadata must meet certain standardization criteria to ensure consistency across all projects, enabling platform super administrators to conduct effective analysis later on.
- Handling ODK form updates:
Every time the ODK form changes, processes must be executed to store the already registered metadata so that it can be reloaded after the update. This is necessary because the database needs to be reconstructed from scratch for proper functionality.
- Risk of data loss during updates:
If the update involves changes in column names, structure types, or data types, it could lead to the loss of previously recorded metadata.
- Metadata-Project association:
A method must be devised to relate the metadata registered in Enketo with a corresponding project in ClimMob.
- Challenges with using ClimMob users in ODK form:
Using ClimMob users for ODK’s selection lists does not work automatically, requiring procedures that demand time and resources for continuous updates.
Metadata updates based on feedback and progress (Form already implemented in ClimMob):
- Standardization/Uniformity/Integrity of metadata forms for future analysis.
- Users can update data at any time.
- Conditional logic can be applied to the metadata flow based on project type (e.g., showing or omitting questions).
- The relationship between metadata, users, and projects is feasible and fully achievable.
- All notes compiled by Marilyn are implementable to the existing form.
MarManrow
jacobvanetten
Jacob has requested a change in the metadata format for ClimMob trials, suggesting that it should become an ODK (Open Data Kit) form instead of being an integrated module in the interface. He explained that this change would make the metadata more adaptable to various emerging project types, such as variety testing, consumer testing, or agronomic practices. He also highlighted that implementing this change would offer greater flexibility, allowing each project type to have a tailored format for capturing relevant information. To maintain the ODK metadata forms, he suggested that each thematic area have a "thematic coordinator" responsible for managing and updating ClimMob's metadata and libraries.
The MrBot development team will analyze this request and provide feedback.