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
In order to decide which potential members are applicable in the rush process (attended ≥ 4 events...), we need to link listings to a corresponding rush-category in order to pull the data from the rush events in MongoDB. Here are a couple of approaches:
Option 1 (automated) In-progress
create a Listing as per usual
auto-create a rush-category with the same name as the Listing
enable admin to select a different rush-category in the listing settings if needed (e.g. someone created another with the same name...)
Option 2 (manual)
create a rush-categoryFIRST (must come before Listing creation)
when creating a Listing force the admin to select the corresponding rush-category from a dropdown
The text was updated successfully, but these errors were encountered:
Summary
In order to decide which potential members are applicable in the rush process (attended ≥ 4 events...), we need to link
listings
to a correspondingrush-category
in order to pull the data from the rush events in MongoDB. Here are a couple of approaches:Option 1 (automated)
In-progress
Listing
as per usualrush-category
with the same name as theListing
rush-category
in the listing settings if needed (e.g. someone created another with the same name...)Option 2 (manual)
rush-category
FIRST (must come beforeListing
creation)Listing
force the admin to select the correspondingrush-category
from a dropdownThe text was updated successfully, but these errors were encountered: