This is a private repository for handling issues related to the usability of the Aristotle metadata registry. The software itself is at https://github.com/aristotle-mdr/aristotle-metadata-registry.
Task for Sam: No action necessary, but please read and comment.
March 22 - Skype call with Gillian, Andrew Wilson, Craig Hollingsworth. NRC needs a 'very very very simple data dictionary app' in DHIS2 that will allow users to search for and filter data elements. They have needed it for quite a while but were waiting for DHIS2's improved metadata application to be released. It's due on the first week of April (see https://launchpad.net/dhis2/+milestone/2.23), but NRC has reviewed the app and it doesn't meet their needs. So they are deciding what to do now. They plan to create a wireframe to capture their requirements and then talk internally about what to do next.
If they send it out to tender they would address it to the dhis2 experts newsgroup that I belong to. We may also have another conversation about Aristotle. They took a quick look at it before our call and were inclined to dismiss it immediately because it looked so complicated; they are not convinced about the benefits of using international standards for metadata. By the end of our conversation they were cautiously interested in the benefits, but wanted to be protected from any unnecessary complexity.
NRC's choices regarding the development of the data dictionary are:
NRC could create their own app, but they have not priced it yet.
NRC could send out an RFP, but don't have a budget.
Here are their requirements for 'phase one':
"We want something very very very simple" (for the users).
Table of indicators with information about them:
Description
Numerator
Denominator
Category combinations
Attributes of data elements to label them internally, e.g., by country, region, which team developed that element, sector, whether it is an outcome or output - generally there are 2 or 3 attributes to each element. PSI data dictionary does not allow for attributes (e.g., extra categories, tagging)
Why? We don't want to give access to metadata app to users but they would need to understand and look for relevant indicators. Also, they would need to search for indicators and then export them in a form that could be inserted into a Word document so that they could show a logframe to their donors.
Phase two:
In future phases, it would be nice to:
have all our indicators in one place, including the ones that are not in DHIS2, like our beneficiaries database.
access them without logging into DHIS2, and export selected indicators in Excel.
have interoperability with other donors who are funding the same field offices and collecting almost the same data.
Simplify the process of configuring DHIS2 by making it easier to create and select indicators - a wizard tool to walk a user through the process of creating an indicator, assigning it to datasets, giving it relevant attributes.
Task for Sam: No action necessary, but please read and comment.
March 22 - Skype call with Gillian, Andrew Wilson, Craig Hollingsworth. NRC needs a 'very very very simple data dictionary app' in DHIS2 that will allow users to search for and filter data elements. They have needed it for quite a while but were waiting for DHIS2's improved metadata application to be released. It's due on the first week of April (see https://launchpad.net/dhis2/+milestone/2.23), but NRC has reviewed the app and it doesn't meet their needs. So they are deciding what to do now. They plan to create a wireframe to capture their requirements and then talk internally about what to do next.
If they send it out to tender they would address it to the dhis2 experts newsgroup that I belong to. We may also have another conversation about Aristotle. They took a quick look at it before our call and were inclined to dismiss it immediately because it looked so complicated; they are not convinced about the benefits of using international standards for metadata. By the end of our conversation they were cautiously interested in the benefits, but wanted to be protected from any unnecessary complexity.
NRC's choices regarding the development of the data dictionary are:
Here are their requirements for 'phase one':
"We want something very very very simple" (for the users). Table of indicators with information about them:
Why? We don't want to give access to metadata app to users but they would need to understand and look for relevant indicators. Also, they would need to search for indicators and then export them in a form that could be inserted into a Word document so that they could show a logframe to their donors.
Phase two:
In future phases, it would be nice to: