COPTR - User contributions [en-gb]

File:ATOM (Access to Memory).png

2019-05-24T02:25:44Z

Pearcemoses: Logo for AtoM (Access to Memory) entry

Logo for AtoM (Access to Memory) entry

ATOM (Access to Memory)

2019-05-23T19:25:34Z

Pearcemoses: /* Influence and take-up */

{{Infobox_tool
|purpose=Web-based tool that supports accessioning, arrangement and description, and access to archival finding aids
|image={{PAGENAMEE}}.png
|homepage=https://www.accesstomemory.org/
|license=GNU Affero General Public License v3.0
|platforms=Linux and Unix, Windows, and MacOS
}}






== Description ==
AtoM is an open-source, multi-lingual, web-based tool for archival accessioning, arrangement, description, and access. It includes a web-based interface that archivists can use to enter information about repository records, accessions, authority records (for provenance, creators), hierarchical archival descriptions (fonds/collection, record group, series, subseries, item, among others), terms (such as subject and place access points, maintained in controlled taxonomies), and functions. AtoM also includes a web-based user interface that the public can use to search and browse the collection descriptions. See: https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-summary-final.pdf and https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-sheet-final.pdf.

== Provider ==

Artefactual Systems (New Westminster, BC, Canada) is the lead developer of AtoM and Archivematica. https://www.artefactual.com

== Licensing and cost ==

All AtoM code is released under a GNU Affero General Public License (A-GPL 3.0) and all related resources (such as the documentation, wiki resources, slides, etc.) are freely available under Creative Commons Share-alike licenses (CC-BY-SA 4.0). Users may customize the code themselves, or contract with Artefactual or other vendors to implement new features and enhancements. All modifications should be made available at no cost to other users, per the A-GPL-v3 license.

== User Experiences ==


== Development Activity ==

AtoM 2.0 grew out of the ICA-AtoM system and was first released in October 2013. Version 2.5 was released in May 2019. Generally, since the 2.0 release there has been one major (feature-based) release and one minor (bug-fix and translation update) release per year. The project remains under active development.

Artefactual is also currently collaborating with the newly formed Access to Memory Foundation (https://www.accesstomemoryfoundation.org) to begin preparing high-level design requirements for AtoM 3, a next-generation version of AtoM based on the principles of linked data. Artefactual intends to ensure that there will be an upgrade path from AtoM 2 to AtoM 3, and will continue to maintain AtoM 2 for the foreseeable future, at minimum until there is major feature parity in AtoM 3.



{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

== Platform and interoperability ==

AtoM can run on various Linux distributions and other unix-based platforms, although Artefactual uses Ubuntu long-term support (LTS) releases as the development platform. It can also be installed on Windows and MacOS based servers using virtualization.

Required software includes Nginx (preferred) or Apache, Elasticsearch, Java, MySQL, and Gearman job server. AtoM uses PHP and requires the extensions: cURL, JSON, APC, PDO and PDO-MySQL, and XSL. Other dependencies include ImageMagick, Ghostscript, Ffmpeg, pdftotext (part of poppler-utils) and Apache FOP. Specific versions of those dependencies may vary with the OS and AtoM versions. For more information see: https://www.accesstomemory.org/docs/latest/admin-manual/installation/requirements/.

AtoM can be installed in a virtual machine if the host computer supports virtualization. Note: older Wintel machines may not support virtualization, and many newer Wintel machines need to have virtualization enabled in the BIOS.

AtoM integrates well with Archivematica, the open source digital preservation system also developed by Artefacual Systems. See Archivematica’s COPTR entry here: http://coptr.digipres.org/Archivematica.

== Functional notes ==

In general, the first step is to create a description of the archival institution. AtoM allows for multiple institutions to share the same instance, which could be useful for collaboratives or distinct units within larger repositories. A typical workflow would be to create an authority record for the provenance of the collection, accession the fonds/collection (linked to the institution’s record and the provenance record), create a collection-level description, and then add additional levels of description (series, subseries, folder, item).

In some instances, it may make more sense to create folder or item descriptions in an external tool, such as a spreadsheet, and import them to AtoM.

Descriptions and authority records can include links to digital objects (born-digital or digitized records).

AtoM is highly configurable, and almost all terms appearing in drop-down menus and autocomplete fields in the edit templates are terms that users can edit in the related controlled taxonomies, or related entities that can be edited via the user interface. Administrators can also customize menus, default page elements, and configure a number of additional settings that affect the look and behavior of AtoM. The default theme can be customized, and one alternative theme is included at installation for reference, which can be switched via the user interface. More advanced customization may require editing associated style-sheets or PHP code.

== Documentation and user support ==

Extensive documentation on the website a user manual with sections for getting started, adding/editing content, accessing content, creating reports, importing and exporting data, and data entry templates. The Administrator manual includes sections on installation, maintenance, customization, troubleshooting, and security. The Developer manual includes information for programmers who want to modify or develop modules. See: https://www.accesstomemory.org/docs/latest/

AtoM provides an online demonstration site that allows the public to get a feel for both the archivists’ and public interface. Import and upload features are disabled for security purposes. See: https://demo.accesstomemory.org/. AtoM also provides a preconfigured VirtualBox image that can be easily installed using Vagrant software on most operating systems. This local implementation has all features enabled. (Wintel users should ensure virtualization is enabled in BIOS.) See: https://www.accesstomemory.org/docs/latest/dev-manual/env/vagrant/ and https://www.slideshare.net/accesstomemory/atom-and-vagrant-installing-and-configuring-the-atom-vagrant-box-for-local-testing-and-development.

An active User Forum (based on Google Groups) provides a place to ask questions, both technical and functional, as well as learn about software developments. A large user community and AtoM developers participate in the group and offer a significant amount of support for free. See: https://wiki.accesstomemory.org/Resources/User_forum.

Artefactual also supplies remote technical support, software hosting, software development, custom theming, data migration, training, and consulting for a fee.

== Usability ==

The web interfaces for routine use by archivists and the public are relatively intuitive and easy to use. Edit templates are derived directly from national and international standards wherever relevant, and include tooltips to assist users drawn directly from the related standard rules. Institutions may want to create a user manual that describes how local practice is applied when using the system; for example, how to encode reference codes (collection, box, and folders).

Importing data from spreadsheets requires UTF-8 encoded CSV files with proper unix-style line endings - Artefactual recommends using LibreOffice Calc as a spreadsheet application over proprietary products such as Microsoft Excel, which commonly use custom encodings and line endings. CSV import templates are available on the AtoM wiki https://wiki.accesstomemory.org/Resources/CSV_templates and included in AtoM’s code base as well.

== Expertise required ==

Archivists should be familiar with descriptive standards and practice. See Standards Compliance below.

Installation requires knowledge of the operating system and familiarity with the unix command-line, including the ability to install and customize software, file systems and permissions. However, the installation documentation is superb, providing step-by-step instructions that most tech-savvy users can follow. Advanced users and system administrators should not have problems following the instructions.

== Standards compliance ==

AtoM supports several descriptive standards, including:

- ISAD(G), 2nd ed. International Council on Archives
- Dublin Core, Version 1.1. Dublin Core Initiative
- MODS, Version 3.3, US Library of Congress
- RAD (Rules for Archival Description) July 2008 version. Canadian Council of Archives
- DACS (Describing Archives: a Content Standard), 2nd ed. Society of American Archivists

AtoM also supports ISAAR(CPF), 2nd ed., the ICA’s standard for archival authority records, ISDIAH, 1st ed., the ICA’s Standard for Describing Institutions with Archival Holdings, and ISDF 1st ed. for describing functions.

Data can be imported and exported in EAD 2002 XML (Encoded Archival Description), , MODS XML, DC (simple) XML, EAC-CPF XML (Encoded Archival Context – Corporate, Personal, Family), CSV (comma separated values), and SKOS (Simple Knowledge Organization System).

== Influence and take-up ==

More than 100 institutions around the world are using AtoM. See: https://wiki.accesstomemory.org/Community/Users and https://www.artefactual.com/clients/.

ATOM (Access to Memory)

2019-05-23T19:24:46Z

Pearcemoses: /* Usability */

{{Infobox_tool
|purpose=Web-based tool that supports accessioning, arrangement and description, and access to archival finding aids
|image={{PAGENAMEE}}.png
|homepage=https://www.accesstomemory.org/
|license=GNU Affero General Public License v3.0
|platforms=Linux and Unix, Windows, and MacOS
}}






== Description ==
AtoM is an open-source, multi-lingual, web-based tool for archival accessioning, arrangement, description, and access. It includes a web-based interface that archivists can use to enter information about repository records, accessions, authority records (for provenance, creators), hierarchical archival descriptions (fonds/collection, record group, series, subseries, item, among others), terms (such as subject and place access points, maintained in controlled taxonomies), and functions. AtoM also includes a web-based user interface that the public can use to search and browse the collection descriptions. See: https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-summary-final.pdf and https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-sheet-final.pdf.

== Provider ==

Artefactual Systems (New Westminster, BC, Canada) is the lead developer of AtoM and Archivematica. https://www.artefactual.com

== Licensing and cost ==

All AtoM code is released under a GNU Affero General Public License (A-GPL 3.0) and all related resources (such as the documentation, wiki resources, slides, etc.) are freely available under Creative Commons Share-alike licenses (CC-BY-SA 4.0). Users may customize the code themselves, or contract with Artefactual or other vendors to implement new features and enhancements. All modifications should be made available at no cost to other users, per the A-GPL-v3 license.

== User Experiences ==


== Development Activity ==

AtoM 2.0 grew out of the ICA-AtoM system and was first released in October 2013. Version 2.5 was released in May 2019. Generally, since the 2.0 release there has been one major (feature-based) release and one minor (bug-fix and translation update) release per year. The project remains under active development.

Artefactual is also currently collaborating with the newly formed Access to Memory Foundation (https://www.accesstomemoryfoundation.org) to begin preparing high-level design requirements for AtoM 3, a next-generation version of AtoM based on the principles of linked data. Artefactual intends to ensure that there will be an upgrade path from AtoM 2 to AtoM 3, and will continue to maintain AtoM 2 for the foreseeable future, at minimum until there is major feature parity in AtoM 3.



{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

== Platform and interoperability ==

AtoM can run on various Linux distributions and other unix-based platforms, although Artefactual uses Ubuntu long-term support (LTS) releases as the development platform. It can also be installed on Windows and MacOS based servers using virtualization.

Required software includes Nginx (preferred) or Apache, Elasticsearch, Java, MySQL, and Gearman job server. AtoM uses PHP and requires the extensions: cURL, JSON, APC, PDO and PDO-MySQL, and XSL. Other dependencies include ImageMagick, Ghostscript, Ffmpeg, pdftotext (part of poppler-utils) and Apache FOP. Specific versions of those dependencies may vary with the OS and AtoM versions. For more information see: https://www.accesstomemory.org/docs/latest/admin-manual/installation/requirements/.

AtoM can be installed in a virtual machine if the host computer supports virtualization. Note: older Wintel machines may not support virtualization, and many newer Wintel machines need to have virtualization enabled in the BIOS.

AtoM integrates well with Archivematica, the open source digital preservation system also developed by Artefacual Systems. See Archivematica’s COPTR entry here: http://coptr.digipres.org/Archivematica.

== Functional notes ==

In general, the first step is to create a description of the archival institution. AtoM allows for multiple institutions to share the same instance, which could be useful for collaboratives or distinct units within larger repositories. A typical workflow would be to create an authority record for the provenance of the collection, accession the fonds/collection (linked to the institution’s record and the provenance record), create a collection-level description, and then add additional levels of description (series, subseries, folder, item).

In some instances, it may make more sense to create folder or item descriptions in an external tool, such as a spreadsheet, and import them to AtoM.

Descriptions and authority records can include links to digital objects (born-digital or digitized records).

AtoM is highly configurable, and almost all terms appearing in drop-down menus and autocomplete fields in the edit templates are terms that users can edit in the related controlled taxonomies, or related entities that can be edited via the user interface. Administrators can also customize menus, default page elements, and configure a number of additional settings that affect the look and behavior of AtoM. The default theme can be customized, and one alternative theme is included at installation for reference, which can be switched via the user interface. More advanced customization may require editing associated style-sheets or PHP code.

== Documentation and user support ==

Extensive documentation on the website a user manual with sections for getting started, adding/editing content, accessing content, creating reports, importing and exporting data, and data entry templates. The Administrator manual includes sections on installation, maintenance, customization, troubleshooting, and security. The Developer manual includes information for programmers who want to modify or develop modules. See: https://www.accesstomemory.org/docs/latest/

AtoM provides an online demonstration site that allows the public to get a feel for both the archivists’ and public interface. Import and upload features are disabled for security purposes. See: https://demo.accesstomemory.org/. AtoM also provides a preconfigured VirtualBox image that can be easily installed using Vagrant software on most operating systems. This local implementation has all features enabled. (Wintel users should ensure virtualization is enabled in BIOS.) See: https://www.accesstomemory.org/docs/latest/dev-manual/env/vagrant/ and https://www.slideshare.net/accesstomemory/atom-and-vagrant-installing-and-configuring-the-atom-vagrant-box-for-local-testing-and-development.

An active User Forum (based on Google Groups) provides a place to ask questions, both technical and functional, as well as learn about software developments. A large user community and AtoM developers participate in the group and offer a significant amount of support for free. See: https://wiki.accesstomemory.org/Resources/User_forum.

Artefactual also supplies remote technical support, software hosting, software development, custom theming, data migration, training, and consulting for a fee.

== Usability ==

The web interfaces for routine use by archivists and the public are relatively intuitive and easy to use. Edit templates are derived directly from national and international standards wherever relevant, and include tooltips to assist users drawn directly from the related standard rules. Institutions may want to create a user manual that describes how local practice is applied when using the system; for example, how to encode reference codes (collection, box, and folders).

Importing data from spreadsheets requires UTF-8 encoded CSV files with proper unix-style line endings - Artefactual recommends using LibreOffice Calc as a spreadsheet application over proprietary products such as Microsoft Excel, which commonly use custom encodings and line endings. CSV import templates are available on the AtoM wiki https://wiki.accesstomemory.org/Resources/CSV_templates and included in AtoM’s code base as well.

== Expertise required ==

Archivists should be familiar with descriptive standards and practice. See Standards Compliance below.

Installation requires knowledge of the operating system and familiarity with the unix command-line, including the ability to install and customize software, file systems and permissions. However, the installation documentation is superb, providing step-by-step instructions that most tech-savvy users can follow. Advanced users and system administrators should not have problems following the instructions.

== Standards compliance ==

AtoM supports several descriptive standards, including:

- ISAD(G), 2nd ed. International Council on Archives
- Dublin Core, Version 1.1. Dublin Core Initiative
- MODS, Version 3.3, US Library of Congress
- RAD (Rules for Archival Description) July 2008 version. Canadian Council of Archives
- DACS (Describing Archives: a Content Standard), 2nd ed. Society of American Archivists

AtoM also supports ISAAR(CPF), 2nd ed., the ICA’s standard for archival authority records, ISDIAH, 1st ed., the ICA’s Standard for Describing Institutions with Archival Holdings, and ISDF 1st ed. for describing functions.

Data can be imported and exported in EAD 2002 XML (Encoded Archival Description), , MODS XML, DC (simple) XML, EAC-CPF XML (Encoded Archival Context – Corporate, Personal, Family), CSV (comma separated values), and SKOS (Simple Knowledge Organization System).

== Influence and take-up ==

More than 100 institutions around the world are using AtoM. See: [https://wiki.accesstomemory.org/Community/Users] and [https://www.artefactual.com/clients/].

ATOM (Access to Memory)

2019-05-23T19:23:29Z

Pearcemoses: /* Documentation and user support */

{{Infobox_tool
|purpose=Web-based tool that supports accessioning, arrangement and description, and access to archival finding aids
|image={{PAGENAMEE}}.png
|homepage=https://www.accesstomemory.org/
|license=GNU Affero General Public License v3.0
|platforms=Linux and Unix, Windows, and MacOS
}}






== Description ==
AtoM is an open-source, multi-lingual, web-based tool for archival accessioning, arrangement, description, and access. It includes a web-based interface that archivists can use to enter information about repository records, accessions, authority records (for provenance, creators), hierarchical archival descriptions (fonds/collection, record group, series, subseries, item, among others), terms (such as subject and place access points, maintained in controlled taxonomies), and functions. AtoM also includes a web-based user interface that the public can use to search and browse the collection descriptions. See: https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-summary-final.pdf and https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-sheet-final.pdf.

== Provider ==

Artefactual Systems (New Westminster, BC, Canada) is the lead developer of AtoM and Archivematica. https://www.artefactual.com

== Licensing and cost ==

All AtoM code is released under a GNU Affero General Public License (A-GPL 3.0) and all related resources (such as the documentation, wiki resources, slides, etc.) are freely available under Creative Commons Share-alike licenses (CC-BY-SA 4.0). Users may customize the code themselves, or contract with Artefactual or other vendors to implement new features and enhancements. All modifications should be made available at no cost to other users, per the A-GPL-v3 license.

== User Experiences ==


== Development Activity ==

AtoM 2.0 grew out of the ICA-AtoM system and was first released in October 2013. Version 2.5 was released in May 2019. Generally, since the 2.0 release there has been one major (feature-based) release and one minor (bug-fix and translation update) release per year. The project remains under active development.

Artefactual is also currently collaborating with the newly formed Access to Memory Foundation (https://www.accesstomemoryfoundation.org) to begin preparing high-level design requirements for AtoM 3, a next-generation version of AtoM based on the principles of linked data. Artefactual intends to ensure that there will be an upgrade path from AtoM 2 to AtoM 3, and will continue to maintain AtoM 2 for the foreseeable future, at minimum until there is major feature parity in AtoM 3.



{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

== Platform and interoperability ==

AtoM can run on various Linux distributions and other unix-based platforms, although Artefactual uses Ubuntu long-term support (LTS) releases as the development platform. It can also be installed on Windows and MacOS based servers using virtualization.

Required software includes Nginx (preferred) or Apache, Elasticsearch, Java, MySQL, and Gearman job server. AtoM uses PHP and requires the extensions: cURL, JSON, APC, PDO and PDO-MySQL, and XSL. Other dependencies include ImageMagick, Ghostscript, Ffmpeg, pdftotext (part of poppler-utils) and Apache FOP. Specific versions of those dependencies may vary with the OS and AtoM versions. For more information see: https://www.accesstomemory.org/docs/latest/admin-manual/installation/requirements/.

AtoM can be installed in a virtual machine if the host computer supports virtualization. Note: older Wintel machines may not support virtualization, and many newer Wintel machines need to have virtualization enabled in the BIOS.

AtoM integrates well with Archivematica, the open source digital preservation system also developed by Artefacual Systems. See Archivematica’s COPTR entry here: http://coptr.digipres.org/Archivematica.

== Functional notes ==

In general, the first step is to create a description of the archival institution. AtoM allows for multiple institutions to share the same instance, which could be useful for collaboratives or distinct units within larger repositories. A typical workflow would be to create an authority record for the provenance of the collection, accession the fonds/collection (linked to the institution’s record and the provenance record), create a collection-level description, and then add additional levels of description (series, subseries, folder, item).

In some instances, it may make more sense to create folder or item descriptions in an external tool, such as a spreadsheet, and import them to AtoM.

Descriptions and authority records can include links to digital objects (born-digital or digitized records).

AtoM is highly configurable, and almost all terms appearing in drop-down menus and autocomplete fields in the edit templates are terms that users can edit in the related controlled taxonomies, or related entities that can be edited via the user interface. Administrators can also customize menus, default page elements, and configure a number of additional settings that affect the look and behavior of AtoM. The default theme can be customized, and one alternative theme is included at installation for reference, which can be switched via the user interface. More advanced customization may require editing associated style-sheets or PHP code.

== Documentation and user support ==

Extensive documentation on the website a user manual with sections for getting started, adding/editing content, accessing content, creating reports, importing and exporting data, and data entry templates. The Administrator manual includes sections on installation, maintenance, customization, troubleshooting, and security. The Developer manual includes information for programmers who want to modify or develop modules. See: https://www.accesstomemory.org/docs/latest/

AtoM provides an online demonstration site that allows the public to get a feel for both the archivists’ and public interface. Import and upload features are disabled for security purposes. See: https://demo.accesstomemory.org/. AtoM also provides a preconfigured VirtualBox image that can be easily installed using Vagrant software on most operating systems. This local implementation has all features enabled. (Wintel users should ensure virtualization is enabled in BIOS.) See: https://www.accesstomemory.org/docs/latest/dev-manual/env/vagrant/ and https://www.slideshare.net/accesstomemory/atom-and-vagrant-installing-and-configuring-the-atom-vagrant-box-for-local-testing-and-development.

An active User Forum (based on Google Groups) provides a place to ask questions, both technical and functional, as well as learn about software developments. A large user community and AtoM developers participate in the group and offer a significant amount of support for free. See: https://wiki.accesstomemory.org/Resources/User_forum.

Artefactual also supplies remote technical support, software hosting, software development, custom theming, data migration, training, and consulting for a fee.

== Usability ==

The web interfaces for routine use by archivists and the public are relatively intuitive and easy to use. Edit templates are derived directly from national and international standards wherever relevant, and include tooltips to assist users drawn directly from the related standard rules. Institutions may want to create a user manual that describes how local practice is applied when using the system; for example, how to encode reference codes (collection, box, and folders).

Importing data from spreadsheets requires UTF-8 encoded CSV files with proper unix-style line endings - Artefactual recommends using LibreOffice Calc as a spreadsheet application over proprietary products such as Microsoft Excel, which commonly use custom encodings and line endings. CSV import templates are available on the AtoM wiki [https://wiki.accesstomemory.org/Resources/CSV_templates] and included in AtoM’s code base as well.

== Expertise required ==

Archivists should be familiar with descriptive standards and practice. See Standards Compliance below.

Installation requires knowledge of the operating system and familiarity with the unix command-line, including the ability to install and customize software, file systems and permissions. However, the installation documentation is superb, providing step-by-step instructions that most tech-savvy users can follow. Advanced users and system administrators should not have problems following the instructions.

== Standards compliance ==

AtoM supports several descriptive standards, including:

- ISAD(G), 2nd ed. International Council on Archives
- Dublin Core, Version 1.1. Dublin Core Initiative
- MODS, Version 3.3, US Library of Congress
- RAD (Rules for Archival Description) July 2008 version. Canadian Council of Archives
- DACS (Describing Archives: a Content Standard), 2nd ed. Society of American Archivists

AtoM also supports ISAAR(CPF), 2nd ed., the ICA’s standard for archival authority records, ISDIAH, 1st ed., the ICA’s Standard for Describing Institutions with Archival Holdings, and ISDF 1st ed. for describing functions.

Data can be imported and exported in EAD 2002 XML (Encoded Archival Description), , MODS XML, DC (simple) XML, EAC-CPF XML (Encoded Archival Context – Corporate, Personal, Family), CSV (comma separated values), and SKOS (Simple Knowledge Organization System).

== Influence and take-up ==

More than 100 institutions around the world are using AtoM. See: [https://wiki.accesstomemory.org/Community/Users] and [https://www.artefactual.com/clients/].

ATOM (Access to Memory)

2019-05-23T19:22:15Z

Pearcemoses: /* Platform and interoperability */

{{Infobox_tool
|purpose=Web-based tool that supports accessioning, arrangement and description, and access to archival finding aids
|image={{PAGENAMEE}}.png
|homepage=https://www.accesstomemory.org/
|license=GNU Affero General Public License v3.0
|platforms=Linux and Unix, Windows, and MacOS
}}






== Description ==
AtoM is an open-source, multi-lingual, web-based tool for archival accessioning, arrangement, description, and access. It includes a web-based interface that archivists can use to enter information about repository records, accessions, authority records (for provenance, creators), hierarchical archival descriptions (fonds/collection, record group, series, subseries, item, among others), terms (such as subject and place access points, maintained in controlled taxonomies), and functions. AtoM also includes a web-based user interface that the public can use to search and browse the collection descriptions. See: https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-summary-final.pdf and https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-sheet-final.pdf.

== Provider ==

Artefactual Systems (New Westminster, BC, Canada) is the lead developer of AtoM and Archivematica. https://www.artefactual.com

== Licensing and cost ==

All AtoM code is released under a GNU Affero General Public License (A-GPL 3.0) and all related resources (such as the documentation, wiki resources, slides, etc.) are freely available under Creative Commons Share-alike licenses (CC-BY-SA 4.0). Users may customize the code themselves, or contract with Artefactual or other vendors to implement new features and enhancements. All modifications should be made available at no cost to other users, per the A-GPL-v3 license.

== User Experiences ==


== Development Activity ==

AtoM 2.0 grew out of the ICA-AtoM system and was first released in October 2013. Version 2.5 was released in May 2019. Generally, since the 2.0 release there has been one major (feature-based) release and one minor (bug-fix and translation update) release per year. The project remains under active development.

Artefactual is also currently collaborating with the newly formed Access to Memory Foundation (https://www.accesstomemoryfoundation.org) to begin preparing high-level design requirements for AtoM 3, a next-generation version of AtoM based on the principles of linked data. Artefactual intends to ensure that there will be an upgrade path from AtoM 2 to AtoM 3, and will continue to maintain AtoM 2 for the foreseeable future, at minimum until there is major feature parity in AtoM 3.



{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

== Platform and interoperability ==

AtoM can run on various Linux distributions and other unix-based platforms, although Artefactual uses Ubuntu long-term support (LTS) releases as the development platform. It can also be installed on Windows and MacOS based servers using virtualization.

Required software includes Nginx (preferred) or Apache, Elasticsearch, Java, MySQL, and Gearman job server. AtoM uses PHP and requires the extensions: cURL, JSON, APC, PDO and PDO-MySQL, and XSL. Other dependencies include ImageMagick, Ghostscript, Ffmpeg, pdftotext (part of poppler-utils) and Apache FOP. Specific versions of those dependencies may vary with the OS and AtoM versions. For more information see: https://www.accesstomemory.org/docs/latest/admin-manual/installation/requirements/.

AtoM can be installed in a virtual machine if the host computer supports virtualization. Note: older Wintel machines may not support virtualization, and many newer Wintel machines need to have virtualization enabled in the BIOS.

AtoM integrates well with Archivematica, the open source digital preservation system also developed by Artefacual Systems. See Archivematica’s COPTR entry here: http://coptr.digipres.org/Archivematica.

== Functional notes ==

In general, the first step is to create a description of the archival institution. AtoM allows for multiple institutions to share the same instance, which could be useful for collaboratives or distinct units within larger repositories. A typical workflow would be to create an authority record for the provenance of the collection, accession the fonds/collection (linked to the institution’s record and the provenance record), create a collection-level description, and then add additional levels of description (series, subseries, folder, item).

In some instances, it may make more sense to create folder or item descriptions in an external tool, such as a spreadsheet, and import them to AtoM.

Descriptions and authority records can include links to digital objects (born-digital or digitized records).

AtoM is highly configurable, and almost all terms appearing in drop-down menus and autocomplete fields in the edit templates are terms that users can edit in the related controlled taxonomies, or related entities that can be edited via the user interface. Administrators can also customize menus, default page elements, and configure a number of additional settings that affect the look and behavior of AtoM. The default theme can be customized, and one alternative theme is included at installation for reference, which can be switched via the user interface. More advanced customization may require editing associated style-sheets or PHP code.

== Documentation and user support ==

Extensive documentation on the website a user manual with sections for getting started, adding/editing content, accessing content, creating reports, importing and exporting data, and data entry templates. The Administrator manual includes sections on installation, maintenance, customization, troubleshooting, and security. The Developer manual includes information for programmers who want to modify or develop modules. See: [https://www.accesstomemory.org/docs/latest/]

AtoM provides an online demonstration site that allows the public to get a feel for both the archivists’ and public interface. Import and upload features are disabled for security purposes. See: [https://demo.accesstomemory.org/] AtoM also provides a preconfigured VirtualBox image that can be easily installed using Vagrant software on most operating systems. This local implementation has all features enabled. (Wintel users should ensure virtualization is enabled in BIOS.) See: [https://www.accesstomemory.org/docs/latest/dev-manual/env/vagrant/] and [https://www.slideshare.net/accesstomemory/atom-and-vagrant-installing-and-configuring-the-atom-vagrant-box-for-local-testing-and-development].

An active User Forum (based on Google Groups) provides a place to ask questions, both technical and functional, as well as learn about software developments. A large user community and AtoM developers participate in the group and offer a significant amount of support for free. See: [https://wiki.accesstomemory.org/Resources/User_forum]

Artefactual also supplies remote technical support, software hosting, software development, custom theming, data migration, training, and consulting for a fee.

== Usability ==

The web interfaces for routine use by archivists and the public are relatively intuitive and easy to use. Edit templates are derived directly from national and international standards wherever relevant, and include tooltips to assist users drawn directly from the related standard rules. Institutions may want to create a user manual that describes how local practice is applied when using the system; for example, how to encode reference codes (collection, box, and folders).

Importing data from spreadsheets requires UTF-8 encoded CSV files with proper unix-style line endings - Artefactual recommends using LibreOffice Calc as a spreadsheet application over proprietary products such as Microsoft Excel, which commonly use custom encodings and line endings. CSV import templates are available on the AtoM wiki [https://wiki.accesstomemory.org/Resources/CSV_templates] and included in AtoM’s code base as well.

== Expertise required ==

Archivists should be familiar with descriptive standards and practice. See Standards Compliance below.

Installation requires knowledge of the operating system and familiarity with the unix command-line, including the ability to install and customize software, file systems and permissions. However, the installation documentation is superb, providing step-by-step instructions that most tech-savvy users can follow. Advanced users and system administrators should not have problems following the instructions.

== Standards compliance ==

AtoM supports several descriptive standards, including:

- ISAD(G), 2nd ed. International Council on Archives
- Dublin Core, Version 1.1. Dublin Core Initiative
- MODS, Version 3.3, US Library of Congress
- RAD (Rules for Archival Description) July 2008 version. Canadian Council of Archives
- DACS (Describing Archives: a Content Standard), 2nd ed. Society of American Archivists

AtoM also supports ISAAR(CPF), 2nd ed., the ICA’s standard for archival authority records, ISDIAH, 1st ed., the ICA’s Standard for Describing Institutions with Archival Holdings, and ISDF 1st ed. for describing functions.

Data can be imported and exported in EAD 2002 XML (Encoded Archival Description), , MODS XML, DC (simple) XML, EAC-CPF XML (Encoded Archival Context – Corporate, Personal, Family), CSV (comma separated values), and SKOS (Simple Knowledge Organization System).

== Influence and take-up ==

More than 100 institutions around the world are using AtoM. See: [https://wiki.accesstomemory.org/Community/Users] and [https://www.artefactual.com/clients/].

ATOM (Access to Memory)

2019-05-23T19:21:23Z

Pearcemoses: /* Development Activity */

{{Infobox_tool
|purpose=Web-based tool that supports accessioning, arrangement and description, and access to archival finding aids
|image={{PAGENAMEE}}.png
|homepage=https://www.accesstomemory.org/
|license=GNU Affero General Public License v3.0
|platforms=Linux and Unix, Windows, and MacOS
}}






== Description ==
AtoM is an open-source, multi-lingual, web-based tool for archival accessioning, arrangement, description, and access. It includes a web-based interface that archivists can use to enter information about repository records, accessions, authority records (for provenance, creators), hierarchical archival descriptions (fonds/collection, record group, series, subseries, item, among others), terms (such as subject and place access points, maintained in controlled taxonomies), and functions. AtoM also includes a web-based user interface that the public can use to search and browse the collection descriptions. See: https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-summary-final.pdf and https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-sheet-final.pdf.

== Provider ==

Artefactual Systems (New Westminster, BC, Canada) is the lead developer of AtoM and Archivematica. https://www.artefactual.com

== Licensing and cost ==

All AtoM code is released under a GNU Affero General Public License (A-GPL 3.0) and all related resources (such as the documentation, wiki resources, slides, etc.) are freely available under Creative Commons Share-alike licenses (CC-BY-SA 4.0). Users may customize the code themselves, or contract with Artefactual or other vendors to implement new features and enhancements. All modifications should be made available at no cost to other users, per the A-GPL-v3 license.

== User Experiences ==


== Development Activity ==

AtoM 2.0 grew out of the ICA-AtoM system and was first released in October 2013. Version 2.5 was released in May 2019. Generally, since the 2.0 release there has been one major (feature-based) release and one minor (bug-fix and translation update) release per year. The project remains under active development.

Artefactual is also currently collaborating with the newly formed Access to Memory Foundation (https://www.accesstomemoryfoundation.org) to begin preparing high-level design requirements for AtoM 3, a next-generation version of AtoM based on the principles of linked data. Artefactual intends to ensure that there will be an upgrade path from AtoM 2 to AtoM 3, and will continue to maintain AtoM 2 for the foreseeable future, at minimum until there is major feature parity in AtoM 3.



{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

== Platform and interoperability ==

AtoM can run on various Linux distributions and other unix-based platforms, although Artefactual uses Ubuntu long-term support (LTS) releases as the development platform. It can also be installed on Windows and MacOS based servers using virtualization.

Required software includes Nginx (preferred) or Apache, Elasticsearch, Java, MySQL, and Gearman job server. AtoM uses PHP and requires the extensions: cURL, JSON, APC, PDO and PDO-MySQL, and XSL. Other dependencies include ImageMagick, Ghostscript, Ffmpeg, pdftotext (part of poppler-utils) and Apache FOP. Specific versions of those dependencies may vary with the OS and AtoM versions. For more information see: [https://www.accesstomemory.org/docs/latest/admin-manual/installation/requirements/]

AtoM can be installed in a virtual machine if the host computer supports virtualization. Note: older Wintel machines may not support virtualization, and many newer Wintel machines need to have virtualization enabled in the BIOS.

AtoM integrates well with Archivematica, the open source digital preservation system also developed by Artefacual Systems. See Archivematica’s COPTR entry here: [http://coptr.digipres.org/Archivematica].

== Functional notes ==

In general, the first step is to create a description of the archival institution. AtoM allows for multiple institutions to share the same instance, which could be useful for collaboratives or distinct units within larger repositories. A typical workflow would be to create an authority record for the provenance of the collection, accession the fonds/collection (linked to the institution’s record and the provenance record), create a collection-level description, and then add additional levels of description (series, subseries, folder, item).

In some instances, it may make more sense to create folder or item descriptions in an external tool, such as a spreadsheet, and import them to AtoM.

Descriptions and authority records can include links to digital objects (born-digital or digitized records).

AtoM is highly configurable, and almost all terms appearing in drop-down menus and autocomplete fields in the edit templates are terms that users can edit in the related controlled taxonomies, or related entities that can be edited via the user interface. Administrators can also customize menus, default page elements, and configure a number of additional settings that affect the look and behavior of AtoM. The default theme can be customized, and one alternative theme is included at installation for reference, which can be switched via the user interface. More advanced customization may require editing associated style-sheets or PHP code.

== Documentation and user support ==

Extensive documentation on the website a user manual with sections for getting started, adding/editing content, accessing content, creating reports, importing and exporting data, and data entry templates. The Administrator manual includes sections on installation, maintenance, customization, troubleshooting, and security. The Developer manual includes information for programmers who want to modify or develop modules. See: [https://www.accesstomemory.org/docs/latest/]

AtoM provides an online demonstration site that allows the public to get a feel for both the archivists’ and public interface. Import and upload features are disabled for security purposes. See: [https://demo.accesstomemory.org/] AtoM also provides a preconfigured VirtualBox image that can be easily installed using Vagrant software on most operating systems. This local implementation has all features enabled. (Wintel users should ensure virtualization is enabled in BIOS.) See: [https://www.accesstomemory.org/docs/latest/dev-manual/env/vagrant/] and [https://www.slideshare.net/accesstomemory/atom-and-vagrant-installing-and-configuring-the-atom-vagrant-box-for-local-testing-and-development].

An active User Forum (based on Google Groups) provides a place to ask questions, both technical and functional, as well as learn about software developments. A large user community and AtoM developers participate in the group and offer a significant amount of support for free. See: [https://wiki.accesstomemory.org/Resources/User_forum]

Artefactual also supplies remote technical support, software hosting, software development, custom theming, data migration, training, and consulting for a fee.

== Usability ==

The web interfaces for routine use by archivists and the public are relatively intuitive and easy to use. Edit templates are derived directly from national and international standards wherever relevant, and include tooltips to assist users drawn directly from the related standard rules. Institutions may want to create a user manual that describes how local practice is applied when using the system; for example, how to encode reference codes (collection, box, and folders).

Importing data from spreadsheets requires UTF-8 encoded CSV files with proper unix-style line endings - Artefactual recommends using LibreOffice Calc as a spreadsheet application over proprietary products such as Microsoft Excel, which commonly use custom encodings and line endings. CSV import templates are available on the AtoM wiki [https://wiki.accesstomemory.org/Resources/CSV_templates] and included in AtoM’s code base as well.

== Expertise required ==

Archivists should be familiar with descriptive standards and practice. See Standards Compliance below.

Installation requires knowledge of the operating system and familiarity with the unix command-line, including the ability to install and customize software, file systems and permissions. However, the installation documentation is superb, providing step-by-step instructions that most tech-savvy users can follow. Advanced users and system administrators should not have problems following the instructions.

== Standards compliance ==

AtoM supports several descriptive standards, including:

- ISAD(G), 2nd ed. International Council on Archives
- Dublin Core, Version 1.1. Dublin Core Initiative
- MODS, Version 3.3, US Library of Congress
- RAD (Rules for Archival Description) July 2008 version. Canadian Council of Archives
- DACS (Describing Archives: a Content Standard), 2nd ed. Society of American Archivists

AtoM also supports ISAAR(CPF), 2nd ed., the ICA’s standard for archival authority records, ISDIAH, 1st ed., the ICA’s Standard for Describing Institutions with Archival Holdings, and ISDF 1st ed. for describing functions.

Data can be imported and exported in EAD 2002 XML (Encoded Archival Description), , MODS XML, DC (simple) XML, EAC-CPF XML (Encoded Archival Context – Corporate, Personal, Family), CSV (comma separated values), and SKOS (Simple Knowledge Organization System).

== Influence and take-up ==

More than 100 institutions around the world are using AtoM. See: [https://wiki.accesstomemory.org/Community/Users] and [https://www.artefactual.com/clients/].

ATOM (Access to Memory)

2019-05-23T19:20:26Z

Pearcemoses: /* Description */

{{Infobox_tool
|purpose=Web-based tool that supports accessioning, arrangement and description, and access to archival finding aids
|image={{PAGENAMEE}}.png
|homepage=https://www.accesstomemory.org/
|license=GNU Affero General Public License v3.0
|platforms=Linux and Unix, Windows, and MacOS
}}






== Description ==
AtoM is an open-source, multi-lingual, web-based tool for archival accessioning, arrangement, description, and access. It includes a web-based interface that archivists can use to enter information about repository records, accessions, authority records (for provenance, creators), hierarchical archival descriptions (fonds/collection, record group, series, subseries, item, among others), terms (such as subject and place access points, maintained in controlled taxonomies), and functions. AtoM also includes a web-based user interface that the public can use to search and browse the collection descriptions. See: https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-summary-final.pdf and https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-sheet-final.pdf.

== Provider ==

Artefactual Systems (New Westminster, BC, Canada) is the lead developer of AtoM and Archivematica. https://www.artefactual.com

== Licensing and cost ==

All AtoM code is released under a GNU Affero General Public License (A-GPL 3.0) and all related resources (such as the documentation, wiki resources, slides, etc.) are freely available under Creative Commons Share-alike licenses (CC-BY-SA 4.0). Users may customize the code themselves, or contract with Artefactual or other vendors to implement new features and enhancements. All modifications should be made available at no cost to other users, per the A-GPL-v3 license.

== User Experiences ==


== Development Activity ==

AtoM 2.0 grew out of the ICA-AtoM system and was first released in October 2013. Version 2.5 was released in May 2019. Generally, since the 2.0 release there has been one major (feature-based) release and one minor (bug-fix and translation update) release per year. The project remains under active development.

Artefactual is also currently collaborating with the newly formed Access to Memory Foundation [https://www.accesstomemoryfoundation.org] to begin preparing high-level design requirements for AtoM 3, a next-generation version of AtoM based on the principles of linked data. Artefactual intends to ensure that there will be an upgrade path from AtoM 2 to AtoM 3, and will continue to maintain AtoM 2 for the foreseeable future, at minimum until there is major feature parity in AtoM 3.



{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

== Platform and interoperability ==

AtoM can run on various Linux distributions and other unix-based platforms, although Artefactual uses Ubuntu long-term support (LTS) releases as the development platform. It can also be installed on Windows and MacOS based servers using virtualization.

Required software includes Nginx (preferred) or Apache, Elasticsearch, Java, MySQL, and Gearman job server. AtoM uses PHP and requires the extensions: cURL, JSON, APC, PDO and PDO-MySQL, and XSL. Other dependencies include ImageMagick, Ghostscript, Ffmpeg, pdftotext (part of poppler-utils) and Apache FOP. Specific versions of those dependencies may vary with the OS and AtoM versions. For more information see: [https://www.accesstomemory.org/docs/latest/admin-manual/installation/requirements/]

AtoM can be installed in a virtual machine if the host computer supports virtualization. Note: older Wintel machines may not support virtualization, and many newer Wintel machines need to have virtualization enabled in the BIOS.

AtoM integrates well with Archivematica, the open source digital preservation system also developed by Artefacual Systems. See Archivematica’s COPTR entry here: [http://coptr.digipres.org/Archivematica].

== Functional notes ==

In general, the first step is to create a description of the archival institution. AtoM allows for multiple institutions to share the same instance, which could be useful for collaboratives or distinct units within larger repositories. A typical workflow would be to create an authority record for the provenance of the collection, accession the fonds/collection (linked to the institution’s record and the provenance record), create a collection-level description, and then add additional levels of description (series, subseries, folder, item).

In some instances, it may make more sense to create folder or item descriptions in an external tool, such as a spreadsheet, and import them to AtoM.

Descriptions and authority records can include links to digital objects (born-digital or digitized records).

AtoM is highly configurable, and almost all terms appearing in drop-down menus and autocomplete fields in the edit templates are terms that users can edit in the related controlled taxonomies, or related entities that can be edited via the user interface. Administrators can also customize menus, default page elements, and configure a number of additional settings that affect the look and behavior of AtoM. The default theme can be customized, and one alternative theme is included at installation for reference, which can be switched via the user interface. More advanced customization may require editing associated style-sheets or PHP code.

== Documentation and user support ==

Extensive documentation on the website a user manual with sections for getting started, adding/editing content, accessing content, creating reports, importing and exporting data, and data entry templates. The Administrator manual includes sections on installation, maintenance, customization, troubleshooting, and security. The Developer manual includes information for programmers who want to modify or develop modules. See: [https://www.accesstomemory.org/docs/latest/]

AtoM provides an online demonstration site that allows the public to get a feel for both the archivists’ and public interface. Import and upload features are disabled for security purposes. See: [https://demo.accesstomemory.org/] AtoM also provides a preconfigured VirtualBox image that can be easily installed using Vagrant software on most operating systems. This local implementation has all features enabled. (Wintel users should ensure virtualization is enabled in BIOS.) See: [https://www.accesstomemory.org/docs/latest/dev-manual/env/vagrant/] and [https://www.slideshare.net/accesstomemory/atom-and-vagrant-installing-and-configuring-the-atom-vagrant-box-for-local-testing-and-development].

An active User Forum (based on Google Groups) provides a place to ask questions, both technical and functional, as well as learn about software developments. A large user community and AtoM developers participate in the group and offer a significant amount of support for free. See: [https://wiki.accesstomemory.org/Resources/User_forum]

Artefactual also supplies remote technical support, software hosting, software development, custom theming, data migration, training, and consulting for a fee.

== Usability ==

The web interfaces for routine use by archivists and the public are relatively intuitive and easy to use. Edit templates are derived directly from national and international standards wherever relevant, and include tooltips to assist users drawn directly from the related standard rules. Institutions may want to create a user manual that describes how local practice is applied when using the system; for example, how to encode reference codes (collection, box, and folders).

Importing data from spreadsheets requires UTF-8 encoded CSV files with proper unix-style line endings - Artefactual recommends using LibreOffice Calc as a spreadsheet application over proprietary products such as Microsoft Excel, which commonly use custom encodings and line endings. CSV import templates are available on the AtoM wiki [https://wiki.accesstomemory.org/Resources/CSV_templates] and included in AtoM’s code base as well.

== Expertise required ==

Archivists should be familiar with descriptive standards and practice. See Standards Compliance below.

Installation requires knowledge of the operating system and familiarity with the unix command-line, including the ability to install and customize software, file systems and permissions. However, the installation documentation is superb, providing step-by-step instructions that most tech-savvy users can follow. Advanced users and system administrators should not have problems following the instructions.

== Standards compliance ==

AtoM supports several descriptive standards, including:

- ISAD(G), 2nd ed. International Council on Archives
- Dublin Core, Version 1.1. Dublin Core Initiative
- MODS, Version 3.3, US Library of Congress
- RAD (Rules for Archival Description) July 2008 version. Canadian Council of Archives
- DACS (Describing Archives: a Content Standard), 2nd ed. Society of American Archivists

AtoM also supports ISAAR(CPF), 2nd ed., the ICA’s standard for archival authority records, ISDIAH, 1st ed., the ICA’s Standard for Describing Institutions with Archival Holdings, and ISDF 1st ed. for describing functions.

Data can be imported and exported in EAD 2002 XML (Encoded Archival Description), , MODS XML, DC (simple) XML, EAC-CPF XML (Encoded Archival Context – Corporate, Personal, Family), CSV (comma separated values), and SKOS (Simple Knowledge Organization System).

== Influence and take-up ==

More than 100 institutions around the world are using AtoM. See: [https://wiki.accesstomemory.org/Community/Users] and [https://www.artefactual.com/clients/].

ATOM (Access to Memory)

2019-05-23T19:19:45Z

Pearcemoses: /* Provider */

{{Infobox_tool
|purpose=Web-based tool that supports accessioning, arrangement and description, and access to archival finding aids
|image={{PAGENAMEE}}.png
|homepage=https://www.accesstomemory.org/
|license=GNU Affero General Public License v3.0
|platforms=Linux and Unix, Windows, and MacOS
}}






== Description ==
AtoM is an open-source, multi-lingual, web-based tool for archival accessioning, arrangement, description, and access. It includes a web-based interface that archivists can use to enter information about repository records, accessions, authority records (for provenance, creators), hierarchical archival descriptions (fonds/collection, record group, series, subseries, item, among others), terms (such as subject and place access points, maintained in controlled taxonomies), and functions. AtoM also includes a web-based user interface that the public can use to search and browse the collection descriptions. See: https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-summary-final.pdf [https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-summary-final.pdf] and https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-sheet-final.pdf [https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-sheet-final.pdf].

== Provider ==

Artefactual Systems (New Westminster, BC, Canada) is the lead developer of AtoM and Archivematica. https://www.artefactual.com

== Licensing and cost ==

All AtoM code is released under a GNU Affero General Public License (A-GPL 3.0) and all related resources (such as the documentation, wiki resources, slides, etc.) are freely available under Creative Commons Share-alike licenses (CC-BY-SA 4.0). Users may customize the code themselves, or contract with Artefactual or other vendors to implement new features and enhancements. All modifications should be made available at no cost to other users, per the A-GPL-v3 license.

== User Experiences ==


== Development Activity ==

AtoM 2.0 grew out of the ICA-AtoM system and was first released in October 2013. Version 2.5 was released in May 2019. Generally, since the 2.0 release there has been one major (feature-based) release and one minor (bug-fix and translation update) release per year. The project remains under active development.

Artefactual is also currently collaborating with the newly formed Access to Memory Foundation [https://www.accesstomemoryfoundation.org] to begin preparing high-level design requirements for AtoM 3, a next-generation version of AtoM based on the principles of linked data. Artefactual intends to ensure that there will be an upgrade path from AtoM 2 to AtoM 3, and will continue to maintain AtoM 2 for the foreseeable future, at minimum until there is major feature parity in AtoM 3.



{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

== Platform and interoperability ==

AtoM can run on various Linux distributions and other unix-based platforms, although Artefactual uses Ubuntu long-term support (LTS) releases as the development platform. It can also be installed on Windows and MacOS based servers using virtualization.

Required software includes Nginx (preferred) or Apache, Elasticsearch, Java, MySQL, and Gearman job server. AtoM uses PHP and requires the extensions: cURL, JSON, APC, PDO and PDO-MySQL, and XSL. Other dependencies include ImageMagick, Ghostscript, Ffmpeg, pdftotext (part of poppler-utils) and Apache FOP. Specific versions of those dependencies may vary with the OS and AtoM versions. For more information see: [https://www.accesstomemory.org/docs/latest/admin-manual/installation/requirements/]

AtoM can be installed in a virtual machine if the host computer supports virtualization. Note: older Wintel machines may not support virtualization, and many newer Wintel machines need to have virtualization enabled in the BIOS.

AtoM integrates well with Archivematica, the open source digital preservation system also developed by Artefacual Systems. See Archivematica’s COPTR entry here: [http://coptr.digipres.org/Archivematica].

== Functional notes ==

In general, the first step is to create a description of the archival institution. AtoM allows for multiple institutions to share the same instance, which could be useful for collaboratives or distinct units within larger repositories. A typical workflow would be to create an authority record for the provenance of the collection, accession the fonds/collection (linked to the institution’s record and the provenance record), create a collection-level description, and then add additional levels of description (series, subseries, folder, item).

In some instances, it may make more sense to create folder or item descriptions in an external tool, such as a spreadsheet, and import them to AtoM.

Descriptions and authority records can include links to digital objects (born-digital or digitized records).

AtoM is highly configurable, and almost all terms appearing in drop-down menus and autocomplete fields in the edit templates are terms that users can edit in the related controlled taxonomies, or related entities that can be edited via the user interface. Administrators can also customize menus, default page elements, and configure a number of additional settings that affect the look and behavior of AtoM. The default theme can be customized, and one alternative theme is included at installation for reference, which can be switched via the user interface. More advanced customization may require editing associated style-sheets or PHP code.

== Documentation and user support ==

Extensive documentation on the website a user manual with sections for getting started, adding/editing content, accessing content, creating reports, importing and exporting data, and data entry templates. The Administrator manual includes sections on installation, maintenance, customization, troubleshooting, and security. The Developer manual includes information for programmers who want to modify or develop modules. See: [https://www.accesstomemory.org/docs/latest/]

AtoM provides an online demonstration site that allows the public to get a feel for both the archivists’ and public interface. Import and upload features are disabled for security purposes. See: [https://demo.accesstomemory.org/] AtoM also provides a preconfigured VirtualBox image that can be easily installed using Vagrant software on most operating systems. This local implementation has all features enabled. (Wintel users should ensure virtualization is enabled in BIOS.) See: [https://www.accesstomemory.org/docs/latest/dev-manual/env/vagrant/] and [https://www.slideshare.net/accesstomemory/atom-and-vagrant-installing-and-configuring-the-atom-vagrant-box-for-local-testing-and-development].

An active User Forum (based on Google Groups) provides a place to ask questions, both technical and functional, as well as learn about software developments. A large user community and AtoM developers participate in the group and offer a significant amount of support for free. See: [https://wiki.accesstomemory.org/Resources/User_forum]

Artefactual also supplies remote technical support, software hosting, software development, custom theming, data migration, training, and consulting for a fee.

== Usability ==

The web interfaces for routine use by archivists and the public are relatively intuitive and easy to use. Edit templates are derived directly from national and international standards wherever relevant, and include tooltips to assist users drawn directly from the related standard rules. Institutions may want to create a user manual that describes how local practice is applied when using the system; for example, how to encode reference codes (collection, box, and folders).

Importing data from spreadsheets requires UTF-8 encoded CSV files with proper unix-style line endings - Artefactual recommends using LibreOffice Calc as a spreadsheet application over proprietary products such as Microsoft Excel, which commonly use custom encodings and line endings. CSV import templates are available on the AtoM wiki [https://wiki.accesstomemory.org/Resources/CSV_templates] and included in AtoM’s code base as well.

== Expertise required ==

Archivists should be familiar with descriptive standards and practice. See Standards Compliance below.

Installation requires knowledge of the operating system and familiarity with the unix command-line, including the ability to install and customize software, file systems and permissions. However, the installation documentation is superb, providing step-by-step instructions that most tech-savvy users can follow. Advanced users and system administrators should not have problems following the instructions.

== Standards compliance ==

AtoM supports several descriptive standards, including:

- ISAD(G), 2nd ed. International Council on Archives
- Dublin Core, Version 1.1. Dublin Core Initiative
- MODS, Version 3.3, US Library of Congress
- RAD (Rules for Archival Description) July 2008 version. Canadian Council of Archives
- DACS (Describing Archives: a Content Standard), 2nd ed. Society of American Archivists

AtoM also supports ISAAR(CPF), 2nd ed., the ICA’s standard for archival authority records, ISDIAH, 1st ed., the ICA’s Standard for Describing Institutions with Archival Holdings, and ISDF 1st ed. for describing functions.

Data can be imported and exported in EAD 2002 XML (Encoded Archival Description), , MODS XML, DC (simple) XML, EAC-CPF XML (Encoded Archival Context – Corporate, Personal, Family), CSV (comma separated values), and SKOS (Simple Knowledge Organization System).

== Influence and take-up ==

More than 100 institutions around the world are using AtoM. See: [https://wiki.accesstomemory.org/Community/Users] and [https://www.artefactual.com/clients/].

ATOM (Access to Memory)

2019-05-23T19:18:33Z

Pearcemoses: /* Description */

{{Infobox_tool
|purpose=Web-based tool that supports accessioning, arrangement and description, and access to archival finding aids
|image={{PAGENAMEE}}.png
|homepage=https://www.accesstomemory.org/
|license=GNU Affero General Public License v3.0
|platforms=Linux and Unix, Windows, and MacOS
}}






== Description ==
AtoM is an open-source, multi-lingual, web-based tool for archival accessioning, arrangement, description, and access. It includes a web-based interface that archivists can use to enter information about repository records, accessions, authority records (for provenance, creators), hierarchical archival descriptions (fonds/collection, record group, series, subseries, item, among others), terms (such as subject and place access points, maintained in controlled taxonomies), and functions. AtoM also includes a web-based user interface that the public can use to search and browse the collection descriptions. See: https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-summary-final.pdf [https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-summary-final.pdf] and https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-sheet-final.pdf [https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-sheet-final.pdf].

== Provider ==

Artefactual Systems (New Westminster, BC, Canada) is the lead developer of AtoM and Archivematica. [https://www.artefactual.com]

== Licensing and cost ==

All AtoM code is released under a GNU Affero General Public License (A-GPL 3.0) and all related resources (such as the documentation, wiki resources, slides, etc.) are freely available under Creative Commons Share-alike licenses (CC-BY-SA 4.0). Users may customize the code themselves, or contract with Artefactual or other vendors to implement new features and enhancements. All modifications should be made available at no cost to other users, per the A-GPL-v3 license.

== User Experiences ==


== Development Activity ==

AtoM 2.0 grew out of the ICA-AtoM system and was first released in October 2013. Version 2.5 was released in May 2019. Generally, since the 2.0 release there has been one major (feature-based) release and one minor (bug-fix and translation update) release per year. The project remains under active development.

Artefactual is also currently collaborating with the newly formed Access to Memory Foundation [https://www.accesstomemoryfoundation.org] to begin preparing high-level design requirements for AtoM 3, a next-generation version of AtoM based on the principles of linked data. Artefactual intends to ensure that there will be an upgrade path from AtoM 2 to AtoM 3, and will continue to maintain AtoM 2 for the foreseeable future, at minimum until there is major feature parity in AtoM 3.



{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

== Platform and interoperability ==

AtoM can run on various Linux distributions and other unix-based platforms, although Artefactual uses Ubuntu long-term support (LTS) releases as the development platform. It can also be installed on Windows and MacOS based servers using virtualization.

Required software includes Nginx (preferred) or Apache, Elasticsearch, Java, MySQL, and Gearman job server. AtoM uses PHP and requires the extensions: cURL, JSON, APC, PDO and PDO-MySQL, and XSL. Other dependencies include ImageMagick, Ghostscript, Ffmpeg, pdftotext (part of poppler-utils) and Apache FOP. Specific versions of those dependencies may vary with the OS and AtoM versions. For more information see: [https://www.accesstomemory.org/docs/latest/admin-manual/installation/requirements/]

AtoM can be installed in a virtual machine if the host computer supports virtualization. Note: older Wintel machines may not support virtualization, and many newer Wintel machines need to have virtualization enabled in the BIOS.

AtoM integrates well with Archivematica, the open source digital preservation system also developed by Artefacual Systems. See Archivematica’s COPTR entry here: [http://coptr.digipres.org/Archivematica].

== Functional notes ==

In general, the first step is to create a description of the archival institution. AtoM allows for multiple institutions to share the same instance, which could be useful for collaboratives or distinct units within larger repositories. A typical workflow would be to create an authority record for the provenance of the collection, accession the fonds/collection (linked to the institution’s record and the provenance record), create a collection-level description, and then add additional levels of description (series, subseries, folder, item).

In some instances, it may make more sense to create folder or item descriptions in an external tool, such as a spreadsheet, and import them to AtoM.

Descriptions and authority records can include links to digital objects (born-digital or digitized records).

AtoM is highly configurable, and almost all terms appearing in drop-down menus and autocomplete fields in the edit templates are terms that users can edit in the related controlled taxonomies, or related entities that can be edited via the user interface. Administrators can also customize menus, default page elements, and configure a number of additional settings that affect the look and behavior of AtoM. The default theme can be customized, and one alternative theme is included at installation for reference, which can be switched via the user interface. More advanced customization may require editing associated style-sheets or PHP code.

== Documentation and user support ==

Extensive documentation on the website a user manual with sections for getting started, adding/editing content, accessing content, creating reports, importing and exporting data, and data entry templates. The Administrator manual includes sections on installation, maintenance, customization, troubleshooting, and security. The Developer manual includes information for programmers who want to modify or develop modules. See: [https://www.accesstomemory.org/docs/latest/]

AtoM provides an online demonstration site that allows the public to get a feel for both the archivists’ and public interface. Import and upload features are disabled for security purposes. See: [https://demo.accesstomemory.org/] AtoM also provides a preconfigured VirtualBox image that can be easily installed using Vagrant software on most operating systems. This local implementation has all features enabled. (Wintel users should ensure virtualization is enabled in BIOS.) See: [https://www.accesstomemory.org/docs/latest/dev-manual/env/vagrant/] and [https://www.slideshare.net/accesstomemory/atom-and-vagrant-installing-and-configuring-the-atom-vagrant-box-for-local-testing-and-development].

An active User Forum (based on Google Groups) provides a place to ask questions, both technical and functional, as well as learn about software developments. A large user community and AtoM developers participate in the group and offer a significant amount of support for free. See: [https://wiki.accesstomemory.org/Resources/User_forum]

Artefactual also supplies remote technical support, software hosting, software development, custom theming, data migration, training, and consulting for a fee.

== Usability ==

The web interfaces for routine use by archivists and the public are relatively intuitive and easy to use. Edit templates are derived directly from national and international standards wherever relevant, and include tooltips to assist users drawn directly from the related standard rules. Institutions may want to create a user manual that describes how local practice is applied when using the system; for example, how to encode reference codes (collection, box, and folders).

Importing data from spreadsheets requires UTF-8 encoded CSV files with proper unix-style line endings - Artefactual recommends using LibreOffice Calc as a spreadsheet application over proprietary products such as Microsoft Excel, which commonly use custom encodings and line endings. CSV import templates are available on the AtoM wiki [https://wiki.accesstomemory.org/Resources/CSV_templates] and included in AtoM’s code base as well.

== Expertise required ==

Archivists should be familiar with descriptive standards and practice. See Standards Compliance below.

Installation requires knowledge of the operating system and familiarity with the unix command-line, including the ability to install and customize software, file systems and permissions. However, the installation documentation is superb, providing step-by-step instructions that most tech-savvy users can follow. Advanced users and system administrators should not have problems following the instructions.

== Standards compliance ==

AtoM supports several descriptive standards, including:

- ISAD(G), 2nd ed. International Council on Archives
- Dublin Core, Version 1.1. Dublin Core Initiative
- MODS, Version 3.3, US Library of Congress
- RAD (Rules for Archival Description) July 2008 version. Canadian Council of Archives
- DACS (Describing Archives: a Content Standard), 2nd ed. Society of American Archivists

AtoM also supports ISAAR(CPF), 2nd ed., the ICA’s standard for archival authority records, ISDIAH, 1st ed., the ICA’s Standard for Describing Institutions with Archival Holdings, and ISDF 1st ed. for describing functions.

Data can be imported and exported in EAD 2002 XML (Encoded Archival Description), , MODS XML, DC (simple) XML, EAC-CPF XML (Encoded Archival Context – Corporate, Personal, Family), CSV (comma separated values), and SKOS (Simple Knowledge Organization System).

== Influence and take-up ==

More than 100 institutions around the world are using AtoM. See: [https://wiki.accesstomemory.org/Community/Users] and [https://www.artefactual.com/clients/].

ATOM (Access to Memory)

2019-05-23T19:15:35Z

Pearcemoses: Created page with " {{Infobox_tool |purpose=Web-based tool that supports accessioning, arrangement and description, and ac..."

{{Infobox_tool
|purpose=Web-based tool that supports accessioning, arrangement and description, and access to archival finding aids
|image={{PAGENAMEE}}.png
|homepage=https://www.accesstomemory.org/
|license=GNU Affero General Public License v3.0
|platforms=Linux and Unix, Windows, and MacOS
}}






== Description ==
AtoM is an open-source, multi-lingual, web-based tool for archival accessioning, arrangement, description, and access. It includes a web-based interface that archivists can use to enter information about repository records, accessions, authority records (for provenance, creators), hierarchical archival descriptions (fonds/collection, record group, series, subseries, item, among others), terms (such as subject and place access points, maintained in controlled taxonomies), and functions. AtoM also includes a web-based user interface that the public can use to search and browse the collection descriptions. See: [https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-summary-final.pdf] and [https://www.artefactual.com/wp-content/uploads/2018/10/AtoM-information-sheet-final.pdf].

== Provider ==

Artefactual Systems (New Westminster, BC, Canada) is the lead developer of AtoM and Archivematica. [https://www.artefactual.com]

== Licensing and cost ==

All AtoM code is released under a GNU Affero General Public License (A-GPL 3.0) and all related resources (such as the documentation, wiki resources, slides, etc.) are freely available under Creative Commons Share-alike licenses (CC-BY-SA 4.0). Users may customize the code themselves, or contract with Artefactual or other vendors to implement new features and enhancements. All modifications should be made available at no cost to other users, per the A-GPL-v3 license.

== User Experiences ==


== Development Activity ==

AtoM 2.0 grew out of the ICA-AtoM system and was first released in October 2013. Version 2.5 was released in May 2019. Generally, since the 2.0 release there has been one major (feature-based) release and one minor (bug-fix and translation update) release per year. The project remains under active development.

Artefactual is also currently collaborating with the newly formed Access to Memory Foundation [https://www.accesstomemoryfoundation.org] to begin preparing high-level design requirements for AtoM 3, a next-generation version of AtoM based on the principles of linked data. Artefactual intends to ensure that there will be an upgrade path from AtoM 2 to AtoM 3, and will continue to maintain AtoM 2 for the foreseeable future, at minimum until there is major feature parity in AtoM 3.



{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

== Platform and interoperability ==

AtoM can run on various Linux distributions and other unix-based platforms, although Artefactual uses Ubuntu long-term support (LTS) releases as the development platform. It can also be installed on Windows and MacOS based servers using virtualization.

Required software includes Nginx (preferred) or Apache, Elasticsearch, Java, MySQL, and Gearman job server. AtoM uses PHP and requires the extensions: cURL, JSON, APC, PDO and PDO-MySQL, and XSL. Other dependencies include ImageMagick, Ghostscript, Ffmpeg, pdftotext (part of poppler-utils) and Apache FOP. Specific versions of those dependencies may vary with the OS and AtoM versions. For more information see: [https://www.accesstomemory.org/docs/latest/admin-manual/installation/requirements/]

AtoM can be installed in a virtual machine if the host computer supports virtualization. Note: older Wintel machines may not support virtualization, and many newer Wintel machines need to have virtualization enabled in the BIOS.

AtoM integrates well with Archivematica, the open source digital preservation system also developed by Artefacual Systems. See Archivematica’s COPTR entry here: [http://coptr.digipres.org/Archivematica].

== Functional notes ==

In general, the first step is to create a description of the archival institution. AtoM allows for multiple institutions to share the same instance, which could be useful for collaboratives or distinct units within larger repositories. A typical workflow would be to create an authority record for the provenance of the collection, accession the fonds/collection (linked to the institution’s record and the provenance record), create a collection-level description, and then add additional levels of description (series, subseries, folder, item).

In some instances, it may make more sense to create folder or item descriptions in an external tool, such as a spreadsheet, and import them to AtoM.

Descriptions and authority records can include links to digital objects (born-digital or digitized records).

AtoM is highly configurable, and almost all terms appearing in drop-down menus and autocomplete fields in the edit templates are terms that users can edit in the related controlled taxonomies, or related entities that can be edited via the user interface. Administrators can also customize menus, default page elements, and configure a number of additional settings that affect the look and behavior of AtoM. The default theme can be customized, and one alternative theme is included at installation for reference, which can be switched via the user interface. More advanced customization may require editing associated style-sheets or PHP code.

== Documentation and user support ==

Extensive documentation on the website a user manual with sections for getting started, adding/editing content, accessing content, creating reports, importing and exporting data, and data entry templates. The Administrator manual includes sections on installation, maintenance, customization, troubleshooting, and security. The Developer manual includes information for programmers who want to modify or develop modules. See: [https://www.accesstomemory.org/docs/latest/]

AtoM provides an online demonstration site that allows the public to get a feel for both the archivists’ and public interface. Import and upload features are disabled for security purposes. See: [https://demo.accesstomemory.org/] AtoM also provides a preconfigured VirtualBox image that can be easily installed using Vagrant software on most operating systems. This local implementation has all features enabled. (Wintel users should ensure virtualization is enabled in BIOS.) See: [https://www.accesstomemory.org/docs/latest/dev-manual/env/vagrant/] and [https://www.slideshare.net/accesstomemory/atom-and-vagrant-installing-and-configuring-the-atom-vagrant-box-for-local-testing-and-development].

An active User Forum (based on Google Groups) provides a place to ask questions, both technical and functional, as well as learn about software developments. A large user community and AtoM developers participate in the group and offer a significant amount of support for free. See: [https://wiki.accesstomemory.org/Resources/User_forum]

Artefactual also supplies remote technical support, software hosting, software development, custom theming, data migration, training, and consulting for a fee.

== Usability ==

The web interfaces for routine use by archivists and the public are relatively intuitive and easy to use. Edit templates are derived directly from national and international standards wherever relevant, and include tooltips to assist users drawn directly from the related standard rules. Institutions may want to create a user manual that describes how local practice is applied when using the system; for example, how to encode reference codes (collection, box, and folders).

Importing data from spreadsheets requires UTF-8 encoded CSV files with proper unix-style line endings - Artefactual recommends using LibreOffice Calc as a spreadsheet application over proprietary products such as Microsoft Excel, which commonly use custom encodings and line endings. CSV import templates are available on the AtoM wiki [https://wiki.accesstomemory.org/Resources/CSV_templates] and included in AtoM’s code base as well.

== Expertise required ==

Archivists should be familiar with descriptive standards and practice. See Standards Compliance below.

Installation requires knowledge of the operating system and familiarity with the unix command-line, including the ability to install and customize software, file systems and permissions. However, the installation documentation is superb, providing step-by-step instructions that most tech-savvy users can follow. Advanced users and system administrators should not have problems following the instructions.

== Standards compliance ==

AtoM supports several descriptive standards, including:

- ISAD(G), 2nd ed. International Council on Archives
- Dublin Core, Version 1.1. Dublin Core Initiative
- MODS, Version 3.3, US Library of Congress
- RAD (Rules for Archival Description) July 2008 version. Canadian Council of Archives
- DACS (Describing Archives: a Content Standard), 2nd ed. Society of American Archivists

AtoM also supports ISAAR(CPF), 2nd ed., the ICA’s standard for archival authority records, ISDIAH, 1st ed., the ICA’s Standard for Describing Institutions with Archival Holdings, and ISDF 1st ed. for describing functions.

Data can be imported and exported in EAD 2002 XML (Encoded Archival Description), , MODS XML, DC (simple) XML, EAC-CPF XML (Encoded Archival Context – Corporate, Personal, Family), CSV (comma separated values), and SKOS (Simple Knowledge Organization System).

== Influence and take-up ==

More than 100 institutions around the world are using AtoM. See: [https://wiki.accesstomemory.org/Community/Users] and [https://www.artefactual.com/clients/].

ICA-AtoM

2019-05-21T15:37:52Z

Pearcemoses: /* Development activity */

{{Infobox_tool
|purpose=ICA-AtoM allows organisations to create standards-based descriptions of their archival holdings and subsequently publish them to the Web.
|image=
|homepage=http://ica-atom.org/
|license=
|platforms=
}}


[[Category:Metadata Processing]]

= Description =
[http://ica-atom.org/ ICA-AtoM] allows organisations to create standards-based descriptions of their archival holdings and subsequently publish them to the Web.  It was designed to support a wide variety of repository and collection types, providing multi-lingual interfaces and supporting multi-repository implementations.
====Provider====
Managed by Artefactual Systems on behalf of the International Council on Archives
====Licensing and cost====
[http://www.gnu.org/licenses/agpl.html AGPL] – free.
====Development activity====
Version 1.3.2 was released in January 2015. ICA-AtoM was superceded by AtoM 2.0.0 [https://www.accesstomemory.org/], initially released in October 2013, and version 2.5.0 was released in May 2019. [https://www.accesstomemory.org/en/download/] Since the 2.0.0 release, Artefactual, lead developers of ICA-AtoM, have shifted the focus of their development to AtoM 2, and ICA-AtoM is no longer being actively maintained or developed. Legacy ICA-AtoM users can upgrade directly to AtoM 2.x releases following the same upgrade instructions [https://www.accesstomemory.org/docs/latest/admin-manual/installation/upgrading/].

The project advertises funding from a wide variety of sources, including the ICA, UNESCO, the World Bank, and several national archives.

====Platform and interoperability====
ICA-AtoM is a web-based application written in PHP5 using the symfony framework, qubit toolkit, and the Propel object-relation mapping (ORM) framework. The system requires a webserver and database server as well as PHP 5.3 or higher with Multibyte String extension; it recommends Apache webserver and MySQL database engine with PDO extension. Use of a wide range of SQL databases is 'theoretically' possible though not supported (see [https://www.ica-atom.org/doc/Minimum_requirements minimum requirements]).
The software will run in Linux, Mac OS X 10.5 and higher, and Windows; for Windows users the project recommends WAMPServer or XAMPP to configure the system if the required software is not in place.
====Functional notes====
ICA-AtoM creates HTML pages for each item in the repository, serving them to web browsers upon request.  The descriptive records at the heart of the application are stored in a database on the server you have the software installed on.  PHP software code manages requests and responses between the web clients, the application logic, and the application content stored in the database.
The project developed the Qubit Open Information Management Toolkit, based on a symfony framework, to organise the component parts using object orientation and best practice web design patterns.
ICA-AtoM uses the Zend Lucene search engine and ranks search results based on where the search term appears in the record. The interface is available in Dutch, French, Spanish, Slovenian and Polish.
====Documentation and user support====
ICA-Atom provides excellent [http://ica-atom.org/doc/Main_Page documentation], including a user manual, tutorials, a demonstrator download, and a glossary.  The site also links to an extremely active Google discussion group.
====Usability====
The software uses a simple web-based interface, and includes an installer that will check the system and report back if the user needs to upgrade any of the server's technical requirements.
====Expertise required====
Users must have archival accessioning skills, including solid knowledge of metadata standards.
====Standards compliance====
The software is designed around the International Council on Archives’ descriptive standards, including ISAD(G), ISAAR(CPF), ISDIAH, and ISDF.  It is also possible to configure the tool to implement the Dublin Core, EAD, EAC, SKOS, and MODS standards. Rights metadata elements are based on PREMIS.
ICA-AtoM supports OAI-PMH.
====Influence and take-up====
As of October 2012 there were approx 250 institutions running ICA-AtoM; examples include UNESCO, the Montreal Neurological Institute, and the Digital Archive of Research on Thailand. A [http://ica-atom.org/doc/ICA-AtoM_users list of implementation examples ]can be found on the site. 
The ICA-AtoM discussion group has over 250 members as of April 2012.

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=ICA-AtoM
}}

ICA-AtoM

2019-05-21T15:36:09Z

Pearcemoses: /* Development activity */

{{Infobox_tool
|purpose=ICA-AtoM allows organisations to create standards-based descriptions of their archival holdings and subsequently publish them to the Web.
|image=
|homepage=http://ica-atom.org/
|license=
|platforms=
}}


[[Category:Metadata Processing]]

= Description =
[http://ica-atom.org/ ICA-AtoM] allows organisations to create standards-based descriptions of their archival holdings and subsequently publish them to the Web.  It was designed to support a wide variety of repository and collection types, providing multi-lingual interfaces and supporting multi-repository implementations.
====Provider====
Managed by Artefactual Systems on behalf of the International Council on Archives
====Licensing and cost====
[http://www.gnu.org/licenses/agpl.html AGPL] – free.
====Development activity====
Version 1.3.2 was released in January 2015. ICA-AtoM was superceded by AtoM 2.0.0 [https://www.accesstomemory.org/], initially released in October 2013, and version 2.5.0 was released in May 2019. [https://www.accesstomemory.org/en/download/] The project advertises funding from a wide variety of sources, including the ICA, UNESCO, the World Bank, and several national archives.

====Platform and interoperability====
ICA-AtoM is a web-based application written in PHP5 using the symfony framework, qubit toolkit, and the Propel object-relation mapping (ORM) framework. The system requires a webserver and database server as well as PHP 5.3 or higher with Multibyte String extension; it recommends Apache webserver and MySQL database engine with PDO extension. Use of a wide range of SQL databases is 'theoretically' possible though not supported (see [https://www.ica-atom.org/doc/Minimum_requirements minimum requirements]).
The software will run in Linux, Mac OS X 10.5 and higher, and Windows; for Windows users the project recommends WAMPServer or XAMPP to configure the system if the required software is not in place.
====Functional notes====
ICA-AtoM creates HTML pages for each item in the repository, serving them to web browsers upon request.  The descriptive records at the heart of the application are stored in a database on the server you have the software installed on.  PHP software code manages requests and responses between the web clients, the application logic, and the application content stored in the database.
The project developed the Qubit Open Information Management Toolkit, based on a symfony framework, to organise the component parts using object orientation and best practice web design patterns.
ICA-AtoM uses the Zend Lucene search engine and ranks search results based on where the search term appears in the record. The interface is available in Dutch, French, Spanish, Slovenian and Polish.
====Documentation and user support====
ICA-Atom provides excellent [http://ica-atom.org/doc/Main_Page documentation], including a user manual, tutorials, a demonstrator download, and a glossary.  The site also links to an extremely active Google discussion group.
====Usability====
The software uses a simple web-based interface, and includes an installer that will check the system and report back if the user needs to upgrade any of the server's technical requirements.
====Expertise required====
Users must have archival accessioning skills, including solid knowledge of metadata standards.
====Standards compliance====
The software is designed around the International Council on Archives’ descriptive standards, including ISAD(G), ISAAR(CPF), ISDIAH, and ISDF.  It is also possible to configure the tool to implement the Dublin Core, EAD, EAC, SKOS, and MODS standards. Rights metadata elements are based on PREMIS.
ICA-AtoM supports OAI-PMH.
====Influence and take-up====
As of October 2012 there were approx 250 institutions running ICA-AtoM; examples include UNESCO, the Montreal Neurological Institute, and the Digital Archive of Research on Thailand. A [http://ica-atom.org/doc/ICA-AtoM_users list of implementation examples ]can be found on the site. 
The ICA-AtoM discussion group has over 250 members as of April 2012.

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=ICA-AtoM
}}

ICA-AtoM

2019-05-03T16:56:05Z

Pearcemoses: /* Development activity */

{{Infobox_tool
|purpose=ICA-AtoM allows organisations to create standards-based descriptions of their archival holdings and subsequently publish them to the Web.
|image=
|homepage=http://ica-atom.org/
|license=
|platforms=
}}


[[Category:Metadata Processing]]

= Description =
[http://ica-atom.org/ ICA-AtoM] allows organisations to create standards-based descriptions of their archival holdings and subsequently publish them to the Web.  It was designed to support a wide variety of repository and collection types, providing multi-lingual interfaces and supporting multi-repository implementations.
====Provider====
Managed by Artefactual Systems on behalf of the International Council on Archives
====Licensing and cost====
[http://www.gnu.org/licenses/agpl.html AGPL] – free.
====Development activity====
Version 1.3.2 was released in January 2015. ICA-AtoM was superceded by AtoM 2.0 [https://www.accesstomemory.org/], initially released in January 2015, and version 2.4.1 was released in November 2018. [https://www.accesstomemory.org/en/download/] The project advertises funding from a wide variety of sources, including the ICA, UNESCO, the World Bank, and several national archives.

====Platform and interoperability====
ICA-AtoM is a web-based application written in PHP5 using the symfony framework, qubit toolkit, and the Propel object-relation mapping (ORM) framework. The system requires a webserver and database server as well as PHP 5.3 or higher with Multibyte String extension; it recommends Apache webserver and MySQL database engine with PDO extension. Use of a wide range of SQL databases is 'theoretically' possible though not supported (see [https://www.ica-atom.org/doc/Minimum_requirements minimum requirements]).
The software will run in Linux, Mac OS X 10.5 and higher, and Windows; for Windows users the project recommends WAMPServer or XAMPP to configure the system if the required software is not in place.
====Functional notes====
ICA-AtoM creates HTML pages for each item in the repository, serving them to web browsers upon request.  The descriptive records at the heart of the application are stored in a database on the server you have the software installed on.  PHP software code manages requests and responses between the web clients, the application logic, and the application content stored in the database.
The project developed the Qubit Open Information Management Toolkit, based on a symfony framework, to organise the component parts using object orientation and best practice web design patterns.
ICA-AtoM uses the Zend Lucene search engine and ranks search results based on where the search term appears in the record. The interface is available in Dutch, French, Spanish, Slovenian and Polish.
====Documentation and user support====
ICA-Atom provides excellent [http://ica-atom.org/doc/Main_Page documentation], including a user manual, tutorials, a demonstrator download, and a glossary.  The site also links to an extremely active Google discussion group.
====Usability====
The software uses a simple web-based interface, and includes an installer that will check the system and report back if the user needs to upgrade any of the server's technical requirements.
====Expertise required====
Users must have archival accessioning skills, including solid knowledge of metadata standards.
====Standards compliance====
The software is designed around the International Council on Archives’ descriptive standards, including ISAD(G), ISAAR(CPF), ISDIAH, and ISDF.  It is also possible to configure the tool to implement the Dublin Core, EAD, EAC, SKOS, and MODS standards. Rights metadata elements are based on PREMIS.
ICA-AtoM supports OAI-PMH.
====Influence and take-up====
As of October 2012 there were approx 250 institutions running ICA-AtoM; examples include UNESCO, the Montreal Neurological Institute, and the Digital Archive of Research on Thailand. A [http://ica-atom.org/doc/ICA-AtoM_users list of implementation examples ]can be found on the site. 
The ICA-AtoM discussion group has over 250 members as of April 2012.

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=ICA-AtoM
}}

Tree

2019-03-10T06:01:10Z

Pearcemoses: /* User Experiences */

{{Infobox_tool
|purpose=Tree displays the directory structure of a path or of the disk in a drive graphically.
|image=
|homepage=http://technet.microsoft.com/en-us/library/cc771130(WS.10).aspx
|license=
|platforms=
}}


[[Category:Metadata Processing]]

= Description =
“Tree is a recursive directory listing program that produces a depth indented listing of files. With no arguments, tree lists the files in the current directory. When directory arguments are given, tree lists all the files and/or directories found in the given directories each in turn. Upon completion of listing all files/directories found, tree returns the total number of files and/or directories listed.” [https://linux.die.net/man/1/tree]

The tree command on Linux offers numerous output options. One option lists directories and subdirectories. By default, the command traverses the entire directory structure, but an option limits the levels to higher-level directories.. Another options lists the directories and subdirectories with the files they contain. Other options also include the file size, last modified date, and full path. By default, the output uses graphic characters and spacing to clearly represent the hierarchy; but other options can format the output as a flat file more easily imported to other programs.

The Linux tree command has been ported Mac OS X and is available from Homebrew (https://formulae.brew.sh/formula/tree#default).

The tree command native to Windows is fairly limited, with limited options to display just the directory structure or the directory structure and file names. The Linux version of treehas been ported to Windows (http://gnuwin32.sourceforge.net/packages/tree.htm).

tree is run from a command prompt. Stdout can be redirected to other programs or to a file.

= User Experiences =
Running the tree command can give an archivist a high-level overview of how files are organized on a disk or file system. It could also be used to generate quick inventories of disks on receipt as part of an accession record.

= Development Activity =

{{Infobox_tool_details
|ohloh_id=Tree
}}

Tree

2019-03-10T06:00:44Z

Pearcemoses: /* Description */

{{Infobox_tool
|purpose=Tree displays the directory structure of a path or of the disk in a drive graphically.
|image=
|homepage=http://technet.microsoft.com/en-us/library/cc771130(WS.10).aspx
|license=
|platforms=
}}


[[Category:Metadata Processing]]

= Description =
“Tree is a recursive directory listing program that produces a depth indented listing of files. With no arguments, tree lists the files in the current directory. When directory arguments are given, tree lists all the files and/or directories found in the given directories each in turn. Upon completion of listing all files/directories found, tree returns the total number of files and/or directories listed.” [https://linux.die.net/man/1/tree]

The tree command on Linux offers numerous output options. One option lists directories and subdirectories. By default, the command traverses the entire directory structure, but an option limits the levels to higher-level directories.. Another options lists the directories and subdirectories with the files they contain. Other options also include the file size, last modified date, and full path. By default, the output uses graphic characters and spacing to clearly represent the hierarchy; but other options can format the output as a flat file more easily imported to other programs.

The Linux tree command has been ported Mac OS X and is available from Homebrew (https://formulae.brew.sh/formula/tree#default).

The tree command native to Windows is fairly limited, with limited options to display just the directory structure or the directory structure and file names. The Linux version of treehas been ported to Windows (http://gnuwin32.sourceforge.net/packages/tree.htm).

tree is run from a command prompt. Stdout can be redirected to other programs or to a file.

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=Tree
}}

Tree

2019-03-10T06:00:08Z

Pearcemoses: