HAPI FAQ: Migrating from Legacy IEC Data Feeds and Mapping Fields

HAPI FAQ – Migrating from the legacy IEC Data Feeds

What is the unique key in HAPI?

The URN (e.g. iec:pub:27412, iec:proj:12875, iec:doc:343967). ⚠️ The numeric ID inside the URN is not the same as the former Data Feeds ID.

How do I find the former publication ID (ARTNUM)?

Use urnAlt in format iec:artnum:xxxxx. It equals the former <ID>:

ID of the bilingual EN-FR version if one exists,
otherwise ID of the English version.

HTML

<urn>iec:pub:27412</urn>
<urnAlt>iec:std:iec:62368-1:2018-10:::</urnAlt>
<urnAlt>iec:artnum:104773</urnAlt>

Why is there no ARTNUM on each release item (language version)?

ARTNUM is an IEC-only data element; it does not exist at ISO, CEN or CENELEC and cannot be harmonized. All language versions are listed under releaseItems, identified by the publication URN.

Is there a mapping file between URNs and publication references?

Yes: ftp://preview.iec.ch/preview/XML/uricatalogue.xml (reference variants and URN variants per publication). A full ID correspondence table is available on request.

Why are Working Document IDs different?

The former feeds grouped all files of a document in one entry. HAPI has one entry per file, so identifiers differ. A translation table is available on request.

How do legacy Publication fields map to HAPI?

Legacy tag	HAPI element
`ID`	`urn` (+ `urnAlt` `iec:artnum:`)
`REFERENCE`	`reference`
`SEQUENCE`	`sortKey`
`NUMBER` / `PART` / `SECTION`	`stdNumber` / `stdPartNumber` / `stdSection` (present only if valued)
`TR`	`publicationType` + `stdType`
`AMD` / `CORR`	`supplType` (AMD / COR) + `supplNumber`
`ISH`	Project level: `projectRelation` type `INTERPRETS`
`EDITION`	`edition`
`CIRCULATIONDATE`	`publicationDate`
`LANGUAGE`	`languageSettings`
`PROJECTS`	`project/urn`
`URL`, `PAGES`, media type, file size	`releaseItem` (`contentRef/url`, `pages`, `format`, `contentLength`)
`FILEMODIFICATIONDATE`	Change in `checksum`
`STATUS`	`status`
`MRD`	`stabilityDate`
`TITLES`	`title xml:lang`
`ABSTRACTS`	Project level: `abstract`
`PRICECODE`	`priceInfo`
`COMMITTEES`	`committee` (urn + reference)
`ICSCODES`	`classifications` (type ICS)
`LASTMODIFICATIONDATE`	`lastChangeTimestamp`
`REPLACEDBY`	Project level: `projectRelation` type `REPLACED_BY`

No longer used: HEAD, REFERENCE_OLD, FILENAME, URLWEBSTORE, URLLIBRARYSERVER, ISPREVIEW, PREVIEWS.

How do legacy Project fields map to HAPI?

Legacy tag	HAPI element
`ID`	`urn`
`REFERENCE`	`reference` – ⚠️ contains the edition, differs from the publication reference
`AMD`	`supplType` + `supplNumber`, plus `projectRelation` `AMENDS`
`FRAG`	`stdFragment`, plus `projectRelation` `SPLIT_FROM`
`PUBS`	`publications/publication`
`COMMITTEES`	`owner`
`ANWDATE`	`initialProjectDate`
`CURRENT`	`stage` with `status` = `CURRENT`
`PREVIOUS`	`CLOSED` stage just before the CURRENT stage
`NEXT_STAGE_TARGET_DATE`	`PLANNED` stage after CURRENT, also in `nextStage`
`PARALLEL_VOTING`	`projectRelation` type `FRANKFURT_AGREEMENT`
`MODIFICATIONDATE`	`lastChangeTimestamp`
`REMARKS`	No longer used

Which legacy feeds are replaced by the Identity Management API?

IEC Data Feeds: IEC Technical Committees (TC/SC) and IEC Working Groups
API Portal Experts feeders for NCs (IEC and CENELEC users and roles)

⚠️ CENELEC permissions and privileges are not provided by HAPI. A specific release will address this need.