Clarification on Date precission fields and their use

Get Help
2

Hi @miquelmAuupa,

There are two types of date fields used on forms:

  1. Precision date fields where the uitype="plugin" and database schema field type is calendar/byte.
    image

  2. Full date fields where the uitype="formattedtext" or uitype="text" and database schema field type is calendar.
    image

The catalogedDate and date1 fields on the Collection Object table are calendar/byte field types defined as uitype="plugin" in the XML.

The plugin uitype supports the partialDateUI plugin, which allows for date precision to be set on the form. Each field of this type actually has two fields in the schema, one calendar and one byte. For example, date1 is calendar but is accompanied by date1precision which is a byte field type in the table’s schema field list. This is why we use tp=date1Precision initialization in the XML.

Expand for details on plugin fields for providing partial dates

Attributes:

  • default (string, optional)
  • initialize (string, optional)
    • df (string, optional) – Stands for “Date Field”
    • tp (string, optional) – Stands for “Type Precision”
    • defaultPrecision (‘year’ | ‘month-year’ | ‘full’, optional, default: ‘full’)
    • canChangePrecision (true | false, optional, default: false for read-only fields and when in form table; otherwise true)

The dateAccessioned and dateReceived fields on the Accession table are calendar field types defined as uitype="formattedtext" or uitype="text" in the XML. These fields are the more commonly available date field in the schema for a given table.

Fields with these uitypes do not support date precision as they cannot be configured with the partialDateUI plugin in the XML because they lack compatibility with the plugin uitype. This is why you are unable to display a date format other than full date using the fields you mention.

Thank you for reaching out!

– Bronwyn