Print

Print


Dear all,

We (my Agency and IT vendor Omega software that created our archive management application according to our needs) just created EAD 3 compatible XML with information about Agency's fonds and validated it (we used utilities-online.info web page for this purpose). Results was that XML is well formed and valid. Next step would be to enable XML generation function of the application on test environment (and then on production environment)- tests are scheduled for January 5 and 9. I'll send some  follow up at the end of this project. Thank you very, very much for all your kind recommendations.

Kind regards,
Arian

Arian Rajh, PhD, Assist. Prof.
Head of document, records and project management department


Croatian Agency for Medicinal Products and Medical Devices
Ksaverska cesta 4
10 000 Zagreb
Croatia
www.halmed.hr 

Tel: +385 1 48 84 320
Mob: +385 99 263 7899
Fax: +385 1 48 84 110
E-mail: [log in to unmask]

Molim ne ispisujte ovaj e-mail osim ako je to zaista potrebno
Please don't print this email unless you really need to

--- Disclaimer ---
This email and/or any of its attachments, may contain confidential information. It must not be disclosed to any person(s) without authorization. This email is intended for the attention of the named adressee(s). If you are not the intended recipient, please, delete this message immediatelly. Any unauthorized use, distribution, reproduction or publication of this message is forbidden.
-----Original Message-----
From: Arian Rajh [mailto:[log in to unmask]] 
Sent: Wednesday, September 28, 2016 8:39 AM
To: [log in to unmask]
Cc: Arian Rajh
Subject: Re: EAD3 validator

Dear Ruth and Michele,

Thank you very much for your answers. I meant to ask about IT tool created to validate EAD xml file against validation rules stated in tag library. For example, for structured set of records with xml backbone for medicinal products approval, there are several IT tools-validators that validate submissions against validation rules such are presence of elements, name conventions etc. It is a mix between technical and content validation.(Example from my work domain, I work in Croatian version of Food and drugs administration as their archivist). Another example from my work environment - records digitised for us by a third party come with xml files used for transfer of metadata into attributes of records after ingest. We are using FileNet based EDRM system. If xml files are not valid (eg. wrong elements according to xml schema), validation function in ingest process moves packages into SIPerror folder for correction.  

So, there are no validator tool similar to my examples. I'm working on computer generated EAD description from database of my institution (sort of archival management system) and I created for developers of that database and application example of EAD xml file with mapping of elements and database attributes. (Well...it is almost done). I followed EAD3 tag library (for structure and parent-child element related rules). 
Thank you very much for a good advice -   I'll use EAD Round-table
guidelines for additional check of validity before development of EAD creation functionality (https://github.com/saa-ead-roundtable/ead3-toolkit#validating-your-ead-file).

Kind regards,
Arian