This is the home page for all information regarding the setting up of initial processes and procedures for the AAU Data Exchange.
Since becoming a member of the AAU, USF is setting up processes to ensure adherence to AAUDE guidelines and security. This page will contain links to all process and project documentation. The process documentation will describe the processes that USF will go through to ensure compliance with AAU requirements, but also data security, integrity and confidentiality. It will also describe the extent that AAU data can be shared and who may have access to this data.
Process Documentation
Go through all emails in AAUDE Support inbox.
Create a Jira Epic for each new request, with the following details:
Create issue on the ODSAIS project with the AAUDE component.
Fill out the Start date field with the date that request/email was received.
Add all the details received with the request on the Description field.
If known from the request information, add Due date, otherwise this will need to be added when the issue is triaged by the core team.
Add the AD-HOC component for a one time requests.
Add the RECURRING component, for recurring issues.
When issue is triaged by the core team, change issue status to: Ready.
When a team member is actively working on the issue, move to Analysis or Development, as required. - Follow the Jira workflow accordingly.
If the core team decides that the request will not be completed, move the issue to Done and add the NOT DOING component.
Go through all emails in AAUDE Support and Update Jira accordingly.
Move emails to the appropriate folder
Needs Triage if it needs to be addressed at the AAUDE meeting
AAUDE Misc if it is a job posting
Needs Triage if it is data that we are receiving and we have submitted (we are allowed access). This is to let everyone know the data is in.
Needs Triage if the email is regarding rankings.
If it is a follow-up email to an email that is already in an email box, then move it to that box. Unless it is new information that needs to be shared, then it goes to Needs Triage. For example, if we are already working on a request and an email arrives reminding us of the date, then it can eitherfjit is an Ad-Hoc request that we are doing, then move it to the email folder DoingAd-Hoc.
Go through the Needs Triage folder and move things accordingly.
Not Doing if we are not doing something.
Doing Recurring if we are doing a recurring request.
Doing Ad-Hoc if we are doing an ad hoc request.
To Do if this is something that is not an AAUDE data request, but needs to be done.
Go through AAUDE Jira Plan and get updates on all issues that are being worked on.
Discuss other issues as needed.
Update AAUDE Jira Plan with new epics moved to Not Doing, Doing Recurring, Doing Ad Hoc.
Refer to AAUDE Jira Plan that has newly completed items and move them from their current folder of To Do, Doing Recurring, Doing Ad Hoc into the Submission Done folder.
Update the Jira board, moving any completed epic to Done.
AAUDE Project Plan - Used for intake and tracking the complete lifecycle of all AAUDE requests.