source: asadb/template/groups/letters/missing-transition.txt

space-accessstablestage
Last change on this file was 26fd6cf, checked in by ASA Group Database <asa-db@…>, 13 years ago

August 28 derecognition reminder

  • Property mode set to 100644
File size: 3.3 KB
Line 
1{% autoescape off %}
2Hello {{group.name}},
3
4    We're following up on our email from July 31st (see below). You still
5appear to be suspended, and are consequently currently scheduled for
6derecognition *this Friday*.
7
8The following problems (at least) exist with your database entry:
9{% for prob in problems %}* {{prob}}
10{% endfor %}
11
12Please contact us (asa-exec@mit.edu) by this Friday (August 31st) if you wish
13to remain active.  We prefer that you fix the listed problems first, but can
14give you some extra time if needed.
15
16You can view your ASA Database entry at
17https://asa.mit.edu/groups/{{group.pk}}, and the listed president, treasurer,
18and group admin can update it. If they are not available, please contact
19asa-exec@mit.edu promptly, copying your president and officers' list.
20
21If you have any questions or concerns, please contact us at asa-exec@mit.edu.
22Make sure to include your group and database URL (just replying to this email
23is fine).
24
25Thanks,
26Alex Dehnert
27ASA Executive Board
28
29===
30
31Hello again {{group.name}},
32    We contacted you several months ago (see below) informing you that we
33would be suspending you if you did not complete your ASA Database entry
34(https://asa.mit.edu/groups/{{group.pk}}). Since your entry has not yet been
35updated, we have done so.
36
37In particular, the following problems apply:
38[...]
39
40In order to get your group unsuspended, you should first update your database
41entry (again, at https://asa.mit.edu/groups/{{group.pk}}). Once that is
42complete, you should contact us at asa-exec@mit.edu to request un-suspension.
43If you have not done so within a month (that is, by August 31) we may move on
44to derecognition.
45
46Note that, at the moment, only your President (and, if set,
47Treasurer and Group Admins) can update the database. If they are not
48available, please contact asa-exec@mit.edu promptly, copying your president
49and officers' list, and we can give additional people permission.
50
51If you have other questions/difficulties, please don't hesitate to contact
52asa-exec@mit.edu.
53
54Thanks,
55ASA Executive Board
56
57====
58
59Dear officers of {{group.name}},
60   This is a followup to our previous email from a couple of weeks ago.
61You have still not updated your entry in the ASA Database. We have gotten
62complaints from some MIT offices (e.g., Schedules) that this is delaying
63their work, and it also interferes with our own work.
64
65*We will suspend* groups that haven't updated their records --- both main info
66and listed people --- by Wednesday 3/21, unless they have contacted us at
67asa-exec@mit.edu about difficulties doing so. Further penalties may follow
68thereafter.
69
70Offices (e.g., SAO, CAC, and Schedules) are already stopping checking
71the old database for signatories. It's to your advantage to update the
72database *before* you attempt to spend money, reserve spaces, and perform
73other functions that will block on your not having updated the database.
74
75More information about accessing and using the new Database and which
76fields need to be updated is posted at: http://web.mit.edu/asa/database/.
77
78Your group's page can be found at https://asa.mit.edu/groups/{{group.pk}}/.
79
80In particular, we believe that your group's entry has the following issues:
81[...]
82
83We appreciate your cooperation in fixing these quickly. If you believe
84this message to be in error, please be sure to contact us at
85asa-exec@mit.edu.
86
87Thanks,
88The ASA Database team
89{% endautoescape %}
Note: See TracBrowser for help on using the repository browser.