...
3. CollectionSpace date format does not have room for some SMK date information.
The datetype and dateextent fields from the current system describe two sets of strings which are used to help the user generate a display text. If we don't save this data, we cannot present the user with the expected user interface when editing data.
Action: We will not store this data . User can create a new date if they want to edit the old one via our interface extensionwithin the CS schema.
4. Representation of dates in the current system.
...
The current (frequently changing) plan is to map all current fields into Collectionspace, although it . The datetype and dateextent fields (see above) from the current system describe two sets of strings which are used to help the user generate a display text. By mapping these to the 'certainty' and 'qualifier' fields we can present the user with the expected user interface when editing data. It remains to be seen if this constitutes misuse of the 'certainty' and 'qualifier' fields. Beolow CS schema.
Below are some examples.
Globus Group | CS Date Information representation | Example data |
|---|---|---|
Day | Date - association | |
| Date - earliest/single | 26.07.1970 |
| > Date - earliest/single certainty | Day |
| > Date - earliest/single qualifier |
|
| Date - latest |
|
| > Date - latest certainty |
|
| > Date - latest qualifier |
|
| Date - period |
|
| Date text | 26.07.1970 |
...