...
- Each has unique name (cant have same name as data field row)
- Is identifier?
- If is identifier, is it searchable without data field scope?
- i.e. can you just search by netId and get a result (yes). or can you search by zoom user id and get a result without telling the search that the value is a zoom user id (no)
- Is access related?
Three types of data fields
- Informational
- e.g. name, description, email, etc
- Needed for provisioning or UI or WS
- Access related
- e.g. dept, title, school, DN
- Needed for loading groups, jexl scripted groups, provisioning events
- Group - sourced
- A group could be the basis of a data field
- Imagine eduPersonAffiliation-like reference groups that drive flags on a user or a multi-valued set of affiliations: e.g. student, member, alumni
- Makes exposing some access information over UI/WS/provisioning easier
- PIT would still be stored in data field PIT since it is more efficient and consistent API
- Should be a low number of groups
- How to translate from group name to data field value
- How to translate from data field value to group name
- "like" SQL string to select all applicable groups
- Informational
- Assignable to
- Non-groups
- Groups
- Source query/filter would need a way to link to group e.g. by group-name or translation
- Stored locally?
- Stored in PIT?
- If data is not huge volume and doesnt change frequently then yes
- Policies could be based on history of attributes
- NetId changes would be easier to deal with
- PIT retention in days
- If stored in PIT, how many days should be stored. Default to 5 years. Blank means store forever
- Which privacy level
- Multi-valued?
- Calculated?
- If the value needs to be translated from other data field in a script (e.g. description)
- Dynamic? (can be selected only if calculated)
- If a script is needed to evaluate the field, and it depends on env or current user (GrouperSesssion), then it is dynamic. e.g. name is institutional_name if the user can see anything there, or public name if not
- From_sole_source: select the source if populated from one source only
- Data type:
- String (in string lookup table)
- Integer
- Date (millis since 1970 integer)
- Floating point (integer with precision of decimals)
- Could have LOV lookups. e.g. ID, name, display name, description
There are some built in data fields
...