1 / 16

Polish Road to Standardization of Archival Description

Polish Road to Standardization of Archival Description. Central Archives of Historical Records, Warsaw 25 th April 2003 Hubert Wajs. Starting point. „ my archives are unique ”.  Exhibition ( during the brake ) Records are unique, description - not. HISTORY I. Polish form (1948)

quiana
Download Presentation

Polish Road to Standardization of Archival Description

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Polish Road to Standardization of Archival Description Central Archives of Historical Records, Warsaw25th April 2003 Hubert Wajs

  2. Starting point • „my archives are unique”.  Exhibition (during the brake) • Records are unique, description - not

  3. HISTORY I • Polish form (1948) • 9 fields  inventory • ISAD(G) • Translation I (1995)

  4. Polish form v. ISAD(G)

  5. From 26 ISAD(G) elements essential are 6:

  6. FORM (model 1948)

  7. FORM (model 1948)

  8. Introduction of ISAD(G) • ISAD(G) • Translation I (1995) • www.archiwa.gov.pl/agad/ • Translation II (ongoings 2003) • From paper forms to electronic databases: • CDS/ISIS (1990-2003) • DBASE III+ & IV (1993-1999) • FOX & FOXPRO (1995-2000) • MS Access (1997  • XML (2003 

  9. ISAD(G) elements in Introductions to the finding aids. • Name of creator 3.2.1. • Administrative / Biographical history 3.2.2. • Archival history 3.2.3 • Immediate source of acquisition 3.2.4. • Accruals 3.3.3. • System of arrangement 3.3.4. • Conditions governing access 3.4.1 • Related units of descriptions 3.5.3. • Publication note 3.5.4. • Rules or Conventions 3.7.2.

  10. HISTORY II • Polish seminary on metadata (22.05.2001) • Peter Horsman – EAD - MAGIC WORD OR TERROR ? (8.06.2001) • Polish seminary on EAD (07.03.2003) • International seminary on EAD (24-25.04.2003) • RLG Best Practice Guidelines for EAD (ongoings 2003)

  11. EAD structure <ead> <eadheader> <eadid> <filedesc> <titlestmt> <frontmatter> <archdesc> <did> <dsc> <c01>

  12. EAD • Down from component • Where: • <c> or <c1 level = "fonds"> • <c2 level = "series"> • <c3 level = "file"> • Examples:

  13. <?xmlversion="1.0"encoding="UTF-8"?> <?xml-stylesheettype="text/css"href="C03.css"?> <inw> <c03><did> <UNITID>1/1</UNITID> <UNITTITLE>Zbiór listów z XVI i XVII w.</UNITTITLE> <ABSTRACT>List Stanisława Karnkowskiego, biskupa kujawskiego do króla [Stefana Batorego], polecający mu zaufanego człowieka Gauloviusa i zawiadamiający, iż tenże osobiście zda królowi bardziej dokładną relację z różnych spraw.</ABSTRACT> <UNITDATE>1579 V 24</UNITDATE> <PHYSDESC>Oryg.; bifolium pap.</PHYSDESC> <EXTENT>s. 1-2</EXTENT> <NOTE>Odcisk pieczątki sygnetowej przez papier na s. 2; podpis nadawcy.</NOTE> </did></c03> <c03><did>

  14. Are we (here in Poland) ready for EAD ? • Intellectually: • in general terms  YES {if YES then HOW? end if}

  15. HOW? EAD(in XML) INVENTORY INTRODUCTION(*.TXT; *. DOC) <archdes> DESCRIPTION OF SINGLE UNIT(*.DBF) <c>

  16. Are we (here in Poland) ready for EAD ? • Intellectually: • In general • In particular • ”Human factor” • Technically: • Software

More Related