Metadata/Controlled Vocabularies

Flag: ⭐️ Modified: February 14, 2026 7:58 PM Created: September 17, 2025 3:27 PM Master Type: Notes Hide: No Starred: Yes Status: Unassigned

Here’s a set of core IPTC Core (and Extension) fields tailored for a historical photography archive in a DAMS, organized by purpose, plus three example records showing how they’d look in practice.

Recommended IPTC-Compliant Fields

Example Records

Below are three sample CSV-style records illustrating how you might populate these IPTC fields for your DAMS.

Notes on Implementation

• Controlled Vocabularies: Use a maintained list for Keywords and Subject Codes to ensure consistency.
• Date Formats: Store all dates as YYYY-MM-DD to comply with IPTC and DAMS requirements.
• Rights Management: Be explicit in the CopyrightNotice field; for public domain images, note “Public Domain.”
• Linkage: JobID or Object ID ties into TMS Collections; URL points back to your public or staff-only gallery.
• Preservation Tracking: Use SpecialInstructions to guide future handling and MetadataDate for audit trails.

This core set of IPTC-compliant fields will support research discovery, cataloguing precision, user access, and long-term preservation all within your DAMS. Let me know if you’d like to see additional Extension fields (e.g., XML-based IPTC Photo Metadata) or deeper examples!

Here’s an expanded guide addressing your three new requests:

(1) Additional IPTC Extension Fields for a Historical Photography Archive

To go beyond the Core IPTC metadata schema and align with IPTC Extension, consider the following additional fields. These provide richer documentation for rights management, archival history, and detailed descriptions—especially useful in heritage contexts.

These fields are IPTC-compliant, especially when using embedded XMP metadata or more structured DAMS systems. If Pics.io does not natively support all IPTC Extension fields, you can still track them in custom templates and CSV metadata.

(2) Deeper Example Records

Here are three richer example records (CSV-style) using a mix of IPTC Core and Extension fields.

Example 1 – Public Street Scene (1925)

Example 2 – Studio Portrait (1945)

Example 3 – Parade Ephemera (1963)

(3) Alternative Controlled Vocabularies for a Photography Archive

To enhance consistency, searchability, and interoperability across platforms and research communities, consider adopting or referencing these vocabularies in addition to IPTC:

📚 Content/Subject Vocabularies

🧾 Technical & Preservation Standards

🧑‍🎨 Cultural Heritage & Linked Data

Would you like a CSV template combining Core + Extension fields and any of the controlled vocabularies (e.g. dropdowns for Getty TGN or AAT)? I can build that for you next.

Here is a comprehensive metadata template for a historical photography archive that integrates the most relevant IPTC Core, IPTC Extension, and external controlled vocabularies (e.g., Getty AAT, TGN, FAST, LCSH, and Wikidata). The format includes:

• Column name (for use in CSV upload or field mapping)
• Definition
• Recommended controlled vocabulary or format
• Example values (3 example records included below)

🔖 Metadata Template Structure

📂 Example Records

Example 1: Nitrate Negative – Street Scene, 1925

Example 2: Glass Plate Negative – Portrait, 1945

Example 3: Brochure – Veterans Day Parade, 1963

🛠️ Next Steps

If you’d like this as:

• A downloadable CSV file with headers and example rows
• A mapped schema to match a platform like Pics.io, TMS, or another DAMS
• A lookup table for controlled vocabularies with dropdown options

Let me know, and I’ll prepare that for you right away.

Thanks for flagging that — you’re right. The system attempt to generate the “Metadata Schema Mapping” document failed due to a technical issue on my end. Let’s fix that now.

I’ll recreate the full content of that document right here so you can copy, reuse, or request a downloadable version afterward.

📁 Metadata Schema Mapping: Pics.io ↔︎ TMS Collections ↔︎ Controlled Vocabularies

This mapping aligns IPTC Core + Extension metadata with the field structures of:

• Pics.io DAMS
• TMS Collections (by Gallery Systems)
• Archival and preservation best practices

🗂 PART 1: Field Mapping Schema

🔍 PART 2: Controlled Vocabulary Lookup Table

✅ Implementation Tips

• Use these fields to build metadata templates in Pics.io using dropdowns and free text as mapped.
• Map TMS ObjectNumber directly to the Pics.io metadata field labeled TMS Object ID.
• Use authority IDs (e.g., Getty TGN, Wikidata Q-IDs) when possible for future-proofing and semantic search.

Would you like this as:

• A CSV or Excel file for import?
• Preformatted Pics.io metadata template fields for bulk creation?
• A printable PDF or document?

Let me know, and I’ll generate it in the format that suits you best.