Refactor Enumerators

[FlatBallFlyer]

Enumerated valid value lists are present in the project in 2 places. They are used both in the Schema applied to the model, and the Enumerators collection used by the UI for validation lists. This issue will update the
applySchema.js to add code that populats enumerators from the enumerators data. This issue should also update the Mongo Database Standards to describe this implementation.

• Update the enumerators data file to add explanations to values. #48
• Use enumeration values from the enumerators data file in the Schemas.

// Function to inject enumerators into the schema
function injectEnumeratorsIntoSchema(schema, enumeratorsDoc, collectionName) {
  Object.keys(enumeratorsDoc[collectionName]).forEach(attribute => {
    schema.properties[attribute].enum = Object.keys(enumeratorsDoc[collectionName][attribute]);
   }
}

• Remove enum constraints from existing schema's, bumping patch level for each.
  • This may be done over time and can be coordinated with work being done on Active issues.
  • The code should be tolerant of schema's that have enum constraints by removing the existing constraint before adding the data driven constraint.
  • The tolerance specific code should be tagged, and removed after all schema's have been upgraded. At that point the existence of a enum constraint should cause the script to fail-fast.

[FlatBallFlyer]

Person Status values:

• pending - signed up and awaiting a mentor assignment
• active - actively meeting with a mentor
• drip - on a drip follow-up campaign, not active
• archived - soft-delete indicator.

[FlatBallFlyer]

We should change drip to inactive, the drip term has confused many and is only common in sales communities.