Field Museum documentation for EMu workflows, structural changes, testing and standardization.
One set for each module:
We use this to document the discussions and decisions that we make as a user group. Some will lead to structural changes requests and others result in workflow changes. This document stays alive and is intended to be our master documentation for that module. NOTE: Jan 2022. We are currently transitioning this into the wiki section of this repo.
We use this to document development requests for Axiell. A pdf is created when it is sent to Axiell and the googledoc changes version.
We use this to document the creaton of a user group and the registry entries that are necessary to define it.
This is for power users when they want a new group created.
We use this to document the Admin level review of structural changes as returned to us from Axiell. It indicates whether developments to a module have be completed as specified in the corresponding structural changes document or not. Once signed off by the Admin team it is returned to Axiell.
Other IT & Data-handling Resources
- Using Awk and R to parse large datasets
- Fastest Way to Load Data Into PostgreSQL Using Python
- FMNH EMu-Reports repo