- About officers and signatories
- How to update your group's information
- How to update your officer email list?
- Who has permission to modify our database information?
- Why is the transition so manual? Why can't you copy our information for us?
The online ASA Database maintains the official list of individuals fulfilling certain roles in groups.
Change from old Database: the Database sends automatic emails to the Student Activities Office (SAO) and Campus Activities Complex (CAC) when you update relevant roles, so you don't need to also email CAC for office access.
- Go to the Database (MIT Certificates Required)
- Under "My Groups" you will see a list of groups to which you have permissions.
- Click on the name of the group that you would like to edit.
- Click "Update" next to the group name.
- Most information can be updated on this page, to update officers and signatories click the link at the bottom of the page
Change from old Database: you can change the officer email list that is listed in the ASA Database yourself and the Database will send notifications of the change.
We cannot update the members of your officer email list, please see the IS&T mailing list page for more info about changing the list members.
The people who have permission to modify the database are those who are already listed in it as President, Treasurer, or Group Admin. It is not related to the members of your group’s email list. It is very important that old officers add new officers to the database after elections. Unlike the old database, financial signatories cannot currently modify the database » to give officers besides your president and treasurer editing access, add those officers as Group Admins.
While we could do the transition automatically — and, indeed, we wrote code to do a fully-automatic transition that we used to populate our testing databases — we decided we preferred to do a more manual transition. There are two main reason for this.
First, it provides some impetus to keep the information up-to-date. We believe that a large portion of the information in the old database was highly outdated. By having groups input data by hand, we hoped that they would notice information in the old database that was out of date and update it while they were inputting it.
Second, it ensures that information in the database is valid. For example, we want to move towards having Athena lockers, constitutions, and so forth on file for all groups. This is a good opportunity to have groups input that information.
We believe that while this increases the work each group needs to do, it has enough value to be worth doing.