Metadata

What item details are for

Item details are the core descriptive fields that help people recognise, search, filter and use an item correctly. Visible fields depend on the item type and local schema, which may include different field types and different levels of detail for different content.

  • Use item details for stable catalogue information.
  • Use description fields for readable context and discovery text.
  • Use keywords and notes according to local metadata rules.
  • Check rights, credit and warning fields before changing information that affects reuse.
Look For In Sprint
  • The item page shows core fields including iBase ID, Identifier, Title, Type, Source, Date, Coverage and Language.
  • Authorship and usage fields include Creator, Publisher, Contributor, Credit and Rights.
  • Description, Keywords and Notes appear as tabs or panels for descriptive text.

Before editing

  • Open the item from a result list, folder, collection or direct link.
  • Check that the item page is showing editable fields for your role.
  • Check whether the item is locked or already being edited by another user.
  • Confirm that you are editing the correct item type and record.
  • Check local rules before changing rights, credit, consent, source, warning, commerce or geolocation information.
Version note: older iBase guidance describes clicking Edit Item before changing metadata. In the reviewed Sprint item page, users with sufficient permission see editable fields directly, plus an Automatically Save Changes control.

Edit item details

The Item Details area contains the fields most often used for recognition, filtering and search.

  • iBase ID, Identifier, Title and Type help users recognise the item.
  • Source, Date, Coverage and Language support discovery and filtering.
  • Creator, Publisher, Contributor, Credit and Rights describe authorship, attribution and use.
  • Content warnings, commerce options and geolocation fields may appear where configured.
  1. Review the existing values before typing over them.
  2. Update only the fields that need to change.
  3. Use agreed formats for dates, names and identifiers.
  4. Pause after edits where automatic saving is enabled, then check that the displayed value is still correct.
  5. Leave uncertainty in an approved field or note rather than hiding it in unrelated text.

Use descriptions, keywords and notes

Descriptive tabs support different types of text. In Sprint, Description, Keywords and Notes appear as tabs or panels on the item page.

  • Use Description for public or catalogue description text.
  • Use Keywords for searchable terms that are not managed as labels or subjects.
  • Use Notes for internal context according to local policy.
  • Avoid putting private, rights-sensitive or workflow-only information in public-facing description fields.

Good descriptive writing

  • Make the item recognisable without repeating every visible detail.
  • Prefer clear names, dates and places where they are known.
  • Do not guess facts that should be verified.
  • Keep terminology consistent with labels, subjects, suggested keywords and existing records.
  • Review automatically suggested tags before treating them as approved descriptive metadata.

Check the record after editing

  1. Where Automatically Save Changes is active, allow the page to save before moving away.
  2. Reopen or review the item page after editing.
  3. Check title, identifier, rights, credit and warning fields where they were changed.
  4. Use Quick Search or a targeted search to confirm the item can be found using expected terms.
  5. Review a sample of related records if the same metadata convention should apply elsewhere.
Note: if your iBase site shows manual save controls such as Update Item, use those controls before leaving the page. The reviewed Sprint item page used automatic saving.