100 likes | 203 Views
How systems support standards UKAD Forum 27 th march 2014 Malcolm Howitt – axiell alm. AXIELL. How systems support standards. Challenge of multiple standards How standards help – and complicate – software development Benefits for archivists and end users. OUR experience.
E N D
How systems support standardsUKAD Forum 27th march 2014Malcolm Howitt – axiellalm AXIELL
How systems support standards • Challenge of multiple standards • How standards help – and complicate– software development • Benefits for archivists and end users
OURexperience • Few core standards whenwestarted • Applyingmanualprocessesintodatabases • Mostlytraditionalmaterial • Earlyfunding for catalogue projects • Focus moved to public access • Commercial suppliersbecameidentifiedwithspecificsectors • Basedaround standard workflows as well as data standards
Current situation • Wider range of material • Traditional, digitised, born digital • List of standards to support isenormous • Recently been asked about • MARC, EAD, EAC, XML, OAI, ISAAR, ISDF, SRU-CQL, SPECTRUM, ICOM, CDWA, LIDO, XSLT, DC, METS, DIDL, OWL, RDF, PREMIS, ICOM AFRIDOC, CCO, VRA, CHIN, OBJECT ID • Develop a system focussedaroundspecific standards • Scope for integration and sharing
Practical application • Systemsbuiltaround standard workflows and data standards • Customers want to defineown workflows and use own local interpretation of standards • Flexible systems but do theybecome • toocomplicated • and complex • and costly
Opening things up • Balance the gap betweeninternal collections management and external collections exposure • Using standards as a data exchange mechanism • supporting local, national and international services
triangle • Three of us in thisrelationship • supplier, ourcustomer, yourcustomer (end user) • Multi-directionalrelationship • Whateach of us does influences the work of the others
triangle • Supplier brings: • support for workflows, standards, data exchange mechanisms • listeningear, responsive to requirements • proactive approach to development • second guessing? • Customer: • uses and interpretswhat the system offers • appliesthis to public representation of content (bothowned and related) • in an exchangeable and discoverableway • End user: • absorbs, uses, engages withothers, has new expectations
So….. • Standards: • Help us define and createtools to allowour customers to workeffectively and efficiently • Provide a structure withinwhichtheycanwork • Facilitate local interpretation • and public exposure • Give us a way to manage end user expectation • Complete the triangle