This is the place for documentation about the Field Museum's implementation of EMu.
In 2024 we transistioned the majority of our documentation of how to use EMu to this repo, and now make use of issues, discussions and the wiki to document as much as possible. We have moved the documentation templates to the wiki in case anyone wants to use them.
EMu meetings are now documented in the discussion section of the repo. Each is tagged according the the user department, and module. The discussions are divided into the following types:
These discussions are fun mentions of EMu's in the news and can be from anyone.
These discussions are answers to questions that crop up on a regular basis. The answers are generally short and the fixes stable.
These discussions are answers to questions that mostly relate to workflows and broader topics than covered by an FAQ. The answers are generally complex and often have accompanying documents and spreadsheets.
These discussions are the agenda and notes for open meetings of the Field Museum EMu community. These include regularly scheduled EMu hour, EMu User meetings, ad-hoc module working group meetings, topic specific sessions and training. Each meeting may generate questions and these (with their answers) are documented as Q&A discussions. For a full list see the meeting index.
Any member of the EMu community can submit a non-urgent question to a meeting. Each of these has its own discussion item which is (as far as possible) answered at the meeting. If it cannot be answered fully then the user may be asked to create an IT helpdesk ticket and/or a github issue for tracking of any investigations and solutions to the question.
These discussions are used to document any data releated reading that users want to share with each other.
If a user wants a non-urgent report created or updated a discussion may be created, particularly if it is a cross-departmental shared report.
There is one structural changes disucssion for each EMu module. If any discussion leads to a request by a user or group to change or add new functionality to EMu (that is not urgent) then a comment it added for that module. These comments are then held until the next round of funded structural changes is submitted to Axiell for development.
Each module has its own set of wiki pages that documents the use of that module at the Museum. This is where we document any standards and workflows that are agreed by the respective working groups and departments. As well as any structural changes that have been approved and scheduled for development by Axiell.
module | workflows | established standrads
module | workflows | established standrads
module | workflows | established standards | glossary
module | workflows | established standards