You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/design/database_models.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,6 +151,10 @@ organisations) in The Carpentries project. Memberships can be paid. With
151
151
each membership comes a number of fields defining perks like allowable
152
152
number of centrally-organised workshops that don't need to pay fee.
153
153
154
+
Includes a `registration_code` field — a unique code shared with member organisations
155
+
and used by trainees and workshop requesters to identify their membership when submitting
156
+
forms (see [Member Code Enforcement](./projects/2023_member_code_enforcement.md)).
157
+
154
158
### `Airport`
155
159
Represents an airport (used for example to locate instructors).
156
160
@@ -198,6 +202,10 @@ Represents a knowledge domain (like High Performance Computing) a person is enga
198
202
Represents a request for instructor training. Usually these requests come from people
199
203
who are not AMY users.
200
204
205
+
Includes a `member_code` field (the registration code entered by the applicant), which is validated against active memberships, partnerships or account benefits, and a
206
+
`member_code_override` boolean field, which records whether the applicant chose to
207
+
submit despite an invalid member code (see [Member Code Enforcement](./projects/2023_member_code_enforcement.md)).
208
+
201
209
This model falls into `external requests` domain, which also includes `WorkshopRequest`,
202
210
`WorkshopInquiryRequest`, and `SelfOrganisedSubmission`.
203
211
@@ -242,6 +250,10 @@ some common parts were extracted into `CommonRequest` abstract model (mixin).
242
250
### `WorkshopRequest`
243
251
Represents a request for teaching a Carpentries workshop.
244
252
253
+
Includes a `member_code` field for the registration code entered by the requester, which
254
+
is validated against active memberships, partnerships or account benefits when member code enforcement is
255
+
enabled (see [Member Code Enforcement](./projects/2023_member_code_enforcement.md)).
Copy file name to clipboardExpand all lines: docs/users_guide/admin_index.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -199,8 +199,16 @@ A workshop can be requested from a host site, and this information can be used t
199
199
200
200
This will take you to a summary view of the workshop requests, workshop inquiries, or self-organised submissions. Click on the "information" icon at the right of each row to see more details.
201
201
202
+
The workshop requests list includes a filter to find requests submitted by a member organisation that did not include a member code.
!!! note "Member code validation on workshop requests"
207
+
208
+
Workshop requests include a field for a registration (member) code. The code is validated against active memberships, partnerships and account benefits. If the code is invalid or inactive, the form displays an error — unlike training requests, there is no option for the submitter to override an invalid code.
209
+
210
+
When viewing a workshop request detail page, an info box shows the membership associated with the submitted member code (if applicable) and the number of workshops remaining for that membership. If the request is submitted with a member code from a partnership or account benefit, then a link to that model is shown.
211
+
204
212
At the bottom of the request information page, the user has the option to accept or discard the request. All requests should be accepted (unless spam or otherwise inappropriate) so The Carpentries can maintain a history of workshop requests. Events can later be tagged as stalled or cancelled. Choosing "Change state to Accepted" will mark it as accepted in the workshop request list but will not create a new event. Select "Accept and create a new event" to create a new event from this request.
205
213
206
214
This will open a page with a side by side view of the request details and view to create a new event, similar to the general new event page. The new event can be created [manually](#creating-a-new-event-manually) or if available, [from the URL](#creating-a-new-event-from-url), as described above.
@@ -350,16 +358,22 @@ See [section above](#adding-bulk-person-records).
350
358
351
359
#### Accepting Trainee Applications
352
360
353
-
In addition to tracking workshops, AMY also allows us to track applications to instructor training events. [The public facing application is here](https://amy.carpentries.org/forms/request_training/). Applicants are given a registration code if participating in a member training event and should select "Profile Creation for Pre-approved Trainees" using this code. Open applicants will not have a registration code.
361
+
In addition to tracking workshops, AMY also allows us to track applications to instructor training events. [The public facing application is here](https://amy.carpentries.org/forms/request_training/). Applicants are given a registration code if participating in a member training event. Open applicants will not have a registration code.
354
362
355
363
Once an individual submits the form, they receive an email that confirms their application has been received and includes a copy of the individual's responses. An admin user can then view the record by going to Requests --> [Training Requests](https://amy.carpentries.org/requests/training_requests/).
This will display a list of all applications that are *Pending or Accepted* and *Unmatched* to an existing person. Applications can then be searched by individual name, email address, group (registration code), status (pending, accepted, discarded, or withdrawn), affiliation, or location. Affiliation and location searches rely on text strings, so *UCLA* will not return *University of California Los Angeles* and *Joburg ZA* will not return *Johannesburg* or *South Africa*.
360
368
369
+
There is also a filter to show only applications where the applicant submitted with an invalid registration code using the override option (see below). This can be used to manually check these applications.
370
+
361
371

362
372
373
+
!!! note "Member code validation on training requests"
374
+
375
+
AMY validates the registration code entered by applicants. If the code is invalid, inactive, or has no seats remaining (applicable for memberships), the form will display an error. However, applicants may check a box labelled "Continue with registration code marked as invalid" to submit the application anyway.
376
+
363
377
Some trainees will already be in AMY. If there is a record with a matching name and email address, they will show up with a "matched trainee" when you search for them. You can match the application to this trainee, or if the match was incorrect, search for a different Person record or create a new Person.
364
378
365
379

0 commit comments