LibraryCarpentry / lc-data-intro-archives

Data Intro for Archivists
https://librarycarpentry.org/lc-data-intro-archives/
Other
13 stars 12 forks source link

Normalise course content with existing archival competencies (checkout) #18

Open ucsdhealthrevcycle opened 5 years ago

ucsdhealthrevcycle commented 5 years ago

Christopher Felker UCSD Health < https://github.com/LibraryCarpentry/lc-data-intro-archives/issues/18 >

This is a pull request offered as an element in the library carpentries instructor checkout process.

This note seeks to normalise archival practices consistent with the internal / global strategy of The Carpentries. Specifically, I wanted to add this language to contextualise the referenced standards a bit more precisely. this note attaches to this language from "Data intro for Archivists \ Foundations" -

"Preferable are standards that have been ... In archival practice, standards have been developed in order for computers to understand the methods that we use to describe our collections. ISAD(G) – General International Standard Archival Description – has helped archivists to determine how to describe their collections but EAD – Encoded Archival Description – has given archivists a standard way of formatting their description".

In the United States, the Academy of Certified Archivists enumerates 7 (seven) 'knowledge domains' -

\ Domain 1: Selection, Appraisal and Acquisition \ Domain 2: Arrangement and Description \ Domain 3: Reference Services and Access \ Domain 4: Preservation and Protection \ Domain 5: Outreach, Advocacy, and Promotion \ Domain 6: Managing Archival Programs \ Domain 7: Professional, Ethical, and Legal Responsibilities

The Academy's knowledge content reference these points

"K-403 the elements of preservation management and preservation planning, including environmental monitoring, disaster preparedness, in-house conservation, reformatting, data migration, data conversion, and services available through outside vendors",

"K-609 methodologies for gathering and evaluating data about archival functions within one’s own program and programs of other institutions".

There are other national archival certifications (Australia, Canada, Netherlands, Italy, Unined Kingdom) which also have related data standards.

ISAD(G) mentioned above, and ISDIAH (not mentioned) are an international standards \ ISAD(g) < http://bit.ly/2IZRnls > ISDIAH < http://bit.ly/2IS33qx >. It is part of a family of international standards.

The significant trans border archival education and certification organisation is the International Council on Archives / Conseil International des Archives Section for Archival Education and Training /Section pour l'enseignement de l'archivistique et la formation des archivistes https://www.ica.org/en/archival-training.

The work you do in this Carpentries course is 'competency based' [n01]. That said, these skills may very well be included in specific certifications and accreditations (or both).

see Academy of Certified Archivists 2017. Handbook for Archival Certification. International Organization for Standardization 2017. ISO standard 5127 Information and documentation — Foundation and vocabulary https://www.iso.org/obp/ui/#home International Organization for Standardization 2016. ISO standard 15489 Information and documentation -- Records management -- Part 1: General https://www.iso.org/obp/ui/#home International Organization for Standardization 2018. ISO standard 16175 Principles and Functional Requirements for Records in Electronic Office Environments https://www.iso.org/obp/ui/#home International Organization for Standardization 2006. ISO standard 13028 Implementation Guidelines for Digitization of Records https://www.iso.org/obp/ui/#home ISDIAH, International Standard for Describing Institutions with Archival Holdings, Committee of Best Practices and Standards, First edition, 2008 ISAD(G): General International Standard Archival Description, Committee on Descriptive Standards, Second Edition, 2000 M Hoy (International Council on Archives / Conseil International des Archives) 2018. Sources relating to archival and recordkeeping competency and certification and accreditation programs. United Nations 2019. Archives and records management https://archives.un.org/content/policy.

notes

01

ICA definitions

Competencies – the skills, knowledge and behaviour required to work within a profession. These are acquired both through initial education and training and participation in a program of continuing professional development (CPD).

Certification – the method of assessing the competencies of individual members of a profession.

Accreditation – the method of assessing programs and courses established to educate and train potential entrants to a profession.

Sadly, in the 2013 ICA certifications sources, only the Association of Records Managers and Administrators now "ARMA International" uses the term 'data' in defining a core competency. "...the Core Competencies for the Records and Information Management (RIM) Professional ... define the knowledge and skills needed to perform successfully in the profession - ... (5) Information Technology relates to the knowledge and skills necessary to develop, maintain and use information processing systems, software applications and supporting hardware and networks for the processing and distribution of data;" ...

I feel this course would serve learners well by presenting this context, by offering learning badges through the Carpentries assessment group and by aligning the learning with enumerated 'basic' data operations found in ISO standard 5127. These are

< basic data operations \ 3.1.11 iso 5127 > < write \ 3.1.11.01 iso 5127 > < read \ 3.1.11.02 iso 5127 > < data entry \ 3.1.11.03 iso 5127 > < coding \ 3.1.11.04 iso 5127 > < encoding \ 3.1.11.05 iso 5127 > < transformation \ 3.1.11.06 iso 5127 > < copy \ 3.1.11.07 iso 5127 > < duplicate \ 3.1.11.08 iso 5127 > < mapping \ 3.1.11.09 iso 5127 > < migration \ 3.1.11.10 iso 5127 > < modification \ 3.1.11.11 iso 5127 > < linkage \ 3.1.11.12 iso 5127 > < erase \ 3.1.11.13 iso 5127 > < display \ 3.1.11.14 iso 5127 > < integrity \ 3.1.11.15 iso 5127 > < store \ 3.1.11.16 iso 5127 > < access \ 3.1.11.17 iso 5127 > < analysis \ 3.1.11.18 iso 5127 > < archiving \ 3.1.11.19 iso 5127 > < citation \ 3.1.11.20 iso 5127 > < cleaning \ 3.1.11.21 iso 5127 > < curation \ 3.1.11.22 iso 5127 > < deposit \ 3.1.11.23 iso 5127 > < integration \ 3.1.11.24 iso 5127 > < registration \ 3.1.11.25 iso 5127 > < publishing \ 3.1.11.26 iso 5127 > < technology migration \ 3.1.11.27 iso 5127 > < back up \ 3.1.11.28 iso 5127 >

kekoziar commented 5 years ago

Thanks for adding an issue, @ucsdhealthrevcycle. There is a lot of information to unpack in this post, and I'm not ready to comment on the content, but I want to make one clarifying statement. You state at the beginning

This is a pull request

You opened an issue, not a pull request. Issues are great ways to have discussion about and track development within a repository. A pull request proposes specific changes to the repository that can be merged (or within GitHub, discussed, edited, etc)