This table in the Django admin will allow you to create widgets for Import Mapping Rules wizards in the Deposit section or modify an existing one. Each entry in this table in equal to one widget on one Import Mapping Rules wizard. So, if you create a widget for mapping a Title element for MARCXML, this widget will only appear on the MARCXML wizard page. You will need to create another entry if you want a Title widget for an EAD Import Mapping Rules wizard.

Requirements

When creating a new entry in the ProfileField table, you must always:

• Select a foreign key from the DigObjectForm table by using the dropdown menu
• Select a foreign key from the DCXMLFormat table by using the dropdown menu
• Place text in the source_label field
• Check either the use_source_widget or use_complex_widget

Requirements in Django

ProfileField.use_source_widget

This or ProfileField.use_complex_widget must be selected when creating a new entry in the ProfileField table. This will indicate whether there is a text entry box where the user enters the metadata field name for this element.

ProfileField.use_source_widget in Django

ProfileField.use_source_widget in Metadata Hopper

ProfileField.use_complex_widget

This or ProfileField.use_source_widget must be selected when creating a new entry in the ProfileField table. This is a complex widget that may be used in place of the source_widget. The archivist has the option of drawing the value from a metadata field or entering default text. The default is false.

ProfileField.use_complex_widget in Django

ProfileField.use_complex_widget in Metadata Hopper

ProfileField.use_instance_widget

This must be used with ProfileField.use_source widget OR ProfileField.use_complex_widget. It cannot be used alone. If true, places a number drop-down select to indicate instance on form.

ProfileField.use_instance_widget in Django

ProfileField.use_instance_widget in Metadata Hopper

ProfileField.use_instance_all_widget

This must be used with ProfileField.use_source widget OR ProfileField.use_complex_widget AND ProfileField.use_instance_widget. It cannot be used alone. If true, place the option for all in an instance drop-down select.

ProfileField.use_instance_all_widget in Django

ProfileField.use_instance_all_widget in Metadata Hopper

ProfileField.use_filename_widget

This must be used with ProfileField.use_source widget OR ProfileField.use_complex_widget. It cannot be used alone. If true, places checkbox option to use the filename as the source of data rather than the input form. The default is false.

ProfileField.use_filename_widget in Django

ProfileField.use_filename_widget in Metadata Hopper

ProfileField.can_add_widget

This must be used with ProfileField.use_source widget OR ProfileField.use_complex_widget. It cannot be used alone. If true, gives the user the option to add another source field for extracting data. The default is false.

ProfileField.can_add_widget in Django

ProfileField.can_add_widget in Metadata Hopper

ProfileField.use_attribute_widget

This must be used with ProfileField.use_source widget OR ProfileField.use_complex_widget. It cannot be used alone. Determines if an attribute will be requested.

ProfileField.use_attribute_widget in Django

ProfileField.use_attribute_widget in Metadata Hopper

ProfileField.use_attribute_value_widget

This must be used with ProfileField.use_source widget OR ProfileField.use_complex_widget AND ProfileField.use_attribute_widget. It cannot be used alone. This determines if an attribute value will be requested.

ProfileField.use_attribute_value_widget in Django

ProfileField.use_attribute_value_widget in Metadata Hopper