Skip to main content
Version: 3.2.X

Metadata Export (MARCXML & Dublin Core)

The ABCD OPAC is not just a display tool; it acts as a data provider. To support interoperability standards (like OAI-PMH) or simply to allow users to download records in structured formats, you must configure the XML schemas.

This module allows you to define how your database records (MARC, LILACS, etc.) are converted into standard XML formats.

1. MARCXML Configuration​

Script: xml_marc.php

This option defines the schema used to convert records from a MARC database into the MARCXML standard.

Step 1: Define the Global Schema​

The system uses a base template located in the configuration folder named marc.xml.

  • Action: When you access General > XML Metadata Schemas > MARC/XML Schema, the system loads this template.
  • Saving: Upon saving, a file named marc_sch.xml is created in the bases/opac_conf/ folder. This serves as the master template for all databases in the current environment.

Step 2: Generate the Output Format (.pft)​

Access: Database Menu > Export to XML > MARC XML Schema

Since ABCD uses ISIS technology, the XML output is actually generated by a PFT (Print Format). This step converts the XML schema into a PFT script automatically.

  1. Preview: The system displays the generated PFT code based on the marc_sch.xml schema.
  2. Test: You can enter an MFN in the "Test with MFN" box and click Test to see the resulting XML code for a specific record.
  3. Save: When you click Save, the system creates the file marcxml.pft.

File Location: bases/[db]/pfts/[lang]/marcxml.pft (or root pfts depending on setup).

User Access

Once configured, the XML button will appear in the record toolbar, allowing users to view the raw metadata.

2. Dublin Core Configuration​

Script: xml_dc.php

Dublin Core (DC) is a simplified metadata standard used widely for digital repositories. Unlike MARCXML (which is a direct translation), mapping to Dublin Core requires defining which fields in your database correspond to the 15 standard DC elements (Title, Creator, Subject, etc.).

Step 1: Define the Global DC Schema​

Access: General > XML Metadata Schemas > Dublin Core/XML Schema

  • The system loads the base template dc.xml.
  • Saving: Creates opac_conf/dc_sch.xml. This file lists the available Dublin Core tags that will be offered for mapping.

Step 2: Map Database Fields​

Access: Database Menu > Export to XML > Dublin Core XML Schema

Each database must have its own mapping map. The system asks you to associate ABCD tags with DC elements.

File Created: bases/opac_conf/[db]_dcxml.tab

Mapping Syntax: You can assign multiple fields to a single DC element using the pipe | separator.

DC ElementMapping ExampleExplanation
Titlev245Maps the content of Tag 245 to dc:title.
Creatorv100^a|v110^aMaps Tag 100 OR Tag 110 to dc:creator.
Subjectv650Maps Tag 650 to dc:subject.

Handling Subfields: If you need specific subfields, use the standard ISIS subfield syntax with the ^ delimiter.

  • Example: v10^ab (Extracts subfields 'a' and 'b' from Tag 10).

Step 3: Generate the DC Format​

After defining the mapping in Step 2, the system automatically generates the transformation PFT.

  1. Select the database.
  2. The system reads the [db]_dcxml.tab mapping.
  3. It generates the PFT code.
  4. Save: Clicking save creates the dc.pft (or dublinecore.pft) file.

File Location: bases/[db]/pfts/dc.pft

OAI-PMH Requirement

If you plan to use the OAI Data Provider module of ABCD, these files (marcxml.pft and dc.pft) are mandatory. The OAI harvester will fail if the database cannot produce these XML formats.