These slides were presented by Dan Gillean at the first ever AtoM Camp, held at the SFU Harbour Centre in Vancouver, BC, Canada, March 20-22, 2017. For more information on the Camp, see:
https://wiki.accesstomemory.org/Community/Camps/SFU2017
These slides introduce some of the primary Command Line tasks available in Access to Memory (AtoM), which can be used to support site maintenance and troubleshooting. For further information on AtoM CLI tasks, see:
* https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/cli-tools/
* https://www.youtube.com/playlist?list=PLZiwlG5eSMeyeETe15EsEBSu5htPLK-wm
The CLI tasks introduced in these slides are based on the 2.4 AtoM release - some tasks or task options may not be available in earlier releases; tasks may be changed in future releases.
These slides accompanied a presentation by Steve Breker of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
These slides are intended for developers who are interested in modifying the default look and feel of AtoM - known as the Dominion theme - and developing a custom theme plugin. They include some theme examples, how to register a plugin in Symfony, and some ideas of the elements you can modify via theming, with examples.
AtoM and Vagrant: Installing and Configuring the AtoM Vagrant Box for Local T...Artefactual Systems - AtoM
These slides introduce AtoM users to Vagrant, and walk users through the process of installing the the AtoM Vagrant box for local testing and development on a home computer or laptop, regardless of what operating system you use.
WARNINGS:
These slides were last updated in May 2017, using the AtoM 2.4 Vagrant box, which is installed using Ubuntu 16.04. and PHP 7.0. Future versions of AtoM may use a different version of Ubuntu and PHP, which might change some of the command-line tasks used to update the box in Part 2. Be sure to check the AtoM documentation for the most up-to-date information: https://www.accesstomemory.org/docs/latest/
The AtoM Vagrant box is designed for local testing and development - it is NOT PRODUCTION READY and should not be used for long-term data storage. Please see the AtoM documentation for instructions on how to install AtoM on a server for use in your institution.
These slides were first publicly shared as part of the 2019 AtoM Camp, held at the University of Westminster in London, UK, July 15-17, 2019.
The slides include tips, tricks, workarounds, warnings, and gotchas about AtoM that can help orient new users - and hopefully even teach experienced users a couple new things!
For more information about Access to Memory (AtoM), see:
* https://www.accesstomemory.org
Building the Future Together: AtoM3, Governance, and the Sustainability of Op...Artefactual Systems - AtoM
Slides accompanying a presentation given by Dan Gillean on June 7th, 2018 at Open Repositories 2018, held in Bozeman, MT.
Access to Memory is a web-based open source application for standards based description and access. AtoM was first released in 2008 and much of the codebase is now relying on deprecated frameworks and libraries – and at the same time, new standards and technologies are changing how our profession approaches description and access. Currently Artefactual Systems, a Canadian based company, uses a services model to support the project. Artefactual is looking ahead to AtoM3, and considering building a linked data driven platform for archival description and access. As we consider AtoM's next generation, we are also examining governance and maintenance models to sustain the project and better empower our user community as Artefactual wasn't originally intended to be AtoM's organizational home. This presentation will offer some thoughts on existing open source project governance models, challenges, and possibilities for the future. How do we ensure community engagement and project sustainability over time?
Slides accompanying a day-long AtoM and Archivematica workshop, delivered October 17, 2016 at the VII Congresso Nacional de Arquivologia in Fortaleza, Brazil.
These slides introduce AtoM (short for Access to Memory), a flexible, open-source application for standards-based description and access in a multilingual, multi-repository environment.
For more information, visit https://accesstomemory.org/
These slides were first publicly shared as part of the 2019 AtoM Camp, held at the University of Westminster in London, UK, July 15-17, 2019.
They provide users with guidance on how to prepare archival descriptions for import into Access to Memory (AtoM) via CSV import. These slides were prepared against AtoM 2.5, and are accurate for versions 2.3-2.5. Earlier versions may require some minor changes; later releases may introduce changes to the CSV templates not covered here.
You can find the latest CSV import templates for AtoM on our wiki, here:
- https://wiki.accesstomemory.org/Resources/CSV_templates
For more information about Access to Memory (AtoM), see:
- https://www.accesstomemory.org
These slides accompanied a presentation by Dan Gillean and Sara Allain of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
In this session, Dan Gillean covered some of key considerations when preparing to migrate data from a legacy source system into AtoM. The slides cover the steps involved, paying specific attention to AtoM's data model and behaviors that should be considered when preparing your data for import into AtoM.
These slides accompanied a presentation by Dan Gillean and Sara Allain of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
In this session, we took a quick tour of some examples of how AtoM is being implemented by our global community of users. We looked specifically at interesting themes, customizations, or the creative use of existing features such as static pages or repository theming as a way of exploring some of the different ways AtoM can be used. Participants were then invited to come up and show off their AtoM site to the attendees as well.
These slides accompanied a presentation by Steve Breker of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
These slides are intended for developers who are interested in modifying the default look and feel of AtoM - known as the Dominion theme - and developing a custom theme plugin. They include some theme examples, how to register a plugin in Symfony, and some ideas of the elements you can modify via theming, with examples.
AtoM and Vagrant: Installing and Configuring the AtoM Vagrant Box for Local T...Artefactual Systems - AtoM
These slides introduce AtoM users to Vagrant, and walk users through the process of installing the the AtoM Vagrant box for local testing and development on a home computer or laptop, regardless of what operating system you use.
WARNINGS:
These slides were last updated in May 2017, using the AtoM 2.4 Vagrant box, which is installed using Ubuntu 16.04. and PHP 7.0. Future versions of AtoM may use a different version of Ubuntu and PHP, which might change some of the command-line tasks used to update the box in Part 2. Be sure to check the AtoM documentation for the most up-to-date information: https://www.accesstomemory.org/docs/latest/
The AtoM Vagrant box is designed for local testing and development - it is NOT PRODUCTION READY and should not be used for long-term data storage. Please see the AtoM documentation for instructions on how to install AtoM on a server for use in your institution.
These slides were first publicly shared as part of the 2019 AtoM Camp, held at the University of Westminster in London, UK, July 15-17, 2019.
The slides include tips, tricks, workarounds, warnings, and gotchas about AtoM that can help orient new users - and hopefully even teach experienced users a couple new things!
For more information about Access to Memory (AtoM), see:
* https://www.accesstomemory.org
Building the Future Together: AtoM3, Governance, and the Sustainability of Op...Artefactual Systems - AtoM
Slides accompanying a presentation given by Dan Gillean on June 7th, 2018 at Open Repositories 2018, held in Bozeman, MT.
Access to Memory is a web-based open source application for standards based description and access. AtoM was first released in 2008 and much of the codebase is now relying on deprecated frameworks and libraries – and at the same time, new standards and technologies are changing how our profession approaches description and access. Currently Artefactual Systems, a Canadian based company, uses a services model to support the project. Artefactual is looking ahead to AtoM3, and considering building a linked data driven platform for archival description and access. As we consider AtoM's next generation, we are also examining governance and maintenance models to sustain the project and better empower our user community as Artefactual wasn't originally intended to be AtoM's organizational home. This presentation will offer some thoughts on existing open source project governance models, challenges, and possibilities for the future. How do we ensure community engagement and project sustainability over time?
Slides accompanying a day-long AtoM and Archivematica workshop, delivered October 17, 2016 at the VII Congresso Nacional de Arquivologia in Fortaleza, Brazil.
These slides introduce AtoM (short for Access to Memory), a flexible, open-source application for standards-based description and access in a multilingual, multi-repository environment.
For more information, visit https://accesstomemory.org/
These slides were first publicly shared as part of the 2019 AtoM Camp, held at the University of Westminster in London, UK, July 15-17, 2019.
They provide users with guidance on how to prepare archival descriptions for import into Access to Memory (AtoM) via CSV import. These slides were prepared against AtoM 2.5, and are accurate for versions 2.3-2.5. Earlier versions may require some minor changes; later releases may introduce changes to the CSV templates not covered here.
You can find the latest CSV import templates for AtoM on our wiki, here:
- https://wiki.accesstomemory.org/Resources/CSV_templates
For more information about Access to Memory (AtoM), see:
- https://www.accesstomemory.org
These slides accompanied a presentation by Dan Gillean and Sara Allain of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
In this session, Dan Gillean covered some of key considerations when preparing to migrate data from a legacy source system into AtoM. The slides cover the steps involved, paying specific attention to AtoM's data model and behaviors that should be considered when preparing your data for import into AtoM.
These slides accompanied a presentation by Dan Gillean and Sara Allain of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
In this session, we took a quick tour of some examples of how AtoM is being implemented by our global community of users. We looked specifically at interesting themes, customizations, or the creative use of existing features such as static pages or repository theming as a way of exploring some of the different ways AtoM can be used. Participants were then invited to come up and show off their AtoM site to the attendees as well.
These slides accompanied a presentation by Steve Breker of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see: https://wiki.accesstomemory.org/Community/Camps/SJC2017
These slides introduce users to the Access to Memory codebase. You can find AtoM's code at: https://github.com/artefactual/atom/
Access to Memory (AtoM) is an open source web application for standards-based archival description and access - learn more at:
https://www.accesstomemory.org
These slides will provide users with an overview of how search works in AtoM, along with a detailed walkthrough of using the Advanced search panel, and performing Expert searches in AtoM.
The slides were originally created by Dan Gillean, AtoM Program Manager, for use in a series of training workshops delivered July 9-13, 2018 at the University of the Witswatersrand in Johannesburg, South Africa. The slides are based on current functionality in AtoM release 2.4.
These slides accompanied a presentation by Steve Breker of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
These slides provide advanced users with an overview of AtoM's data model, and demonstrate how a graphical user interface application such as MySQL Workbench can be used to explore the AtoM MySQL database from the back-end. The slides include a number of example queries.
Slides accompanying a presentation delivered at the VII Congresso Nacional de Arquivologia in Fortaleza, Brazil, on October 19th, 2016. The slides provide an overview of the AtoM project's history, its maintenance by Artefactual, and its development philosophy, before proceeding to examine the application as a component used in a digital preservation ecosystem. Aspects of ISO 16363:2012, the Audit and Certification of Trustworthy Digital Repositories standard, are used to evaluate how AtoM can support description, management, administration, and access functions when used to maintain a chain of custody in a trustworthy digital repository ecosystem.
These slides accompanied a presentation by Steve Breker of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
These slides are intended for programmers interested in developing new features for Access to Memory. They first provide an overview of the feature development proccess, and then look at the different types of development typically pursued (plugins, CLI tasks, Background jobs, and core features), with tips and suggestions for each.
These slides were presented by Dan Gillean at the first ever AtoM Camp, held at the SFU Harbour Centre in Vancouver, BC, Canada, March 20-22, 2017. For more information on the Camp, see:
https://wiki.accesstomemory.org/Community/Camps/SFU2017
These slides introduce participants to basic commands in the linux/unix command-line interface, for navigation and basic tasks such as reading, creating, deleting, and moving files. The slides were intended as an initial introduction for archivists unfamiliar with using the command-line, prior to teaching them about the command-line tasks available in Access to Memory (AtoM), which can be used for maintenance and troubleshooting.
Alfresco Content Modelling and Policy BehavioursJ V
Alfresco DevCon 2010 (Paris and New York)
This session starts by giving an overview of components of an Alfresco content model. We then examine the various forms of call-backs and hook-points available to the developer and give some examples of how these can be used to enforce custom business logic and model consistency.
Security DevOps - Free pentesters' time to focus on high-hanging fruits // Ha...Christian Schneider
In this session I will present best practices of how open source tools (used in the DevOps and security communities) can be properly chained together to form a framework that can - as part of an agile software development CI chain - perform automated checking of certain security aspects. This does not remove the requirement for manual pentests, but tries to automate early security feedback to developers. Ultimately the aim is to free pentesters’ time by continuously reducing the amount of
recurring (easy to find) default findings, so that pentesters can use
that time to focus on the really high-hanging fruits.
Based on my experience of applying SecDevOps techniques to projects, I will present the glue steps required on every commit and at nightly builds to achieve different levels of depth in automated security testing during the CI workflow.
I will conclude with a "SecDevOps Maturity Model" of different stages of automated security testing and present concrete examples of how to achieve each stage with open source security tools.
Practical information for Alfresco integration with AOS (Sharepoint Protocol), Google Drive, Microsoft 365, ONLYOFFICE and Collabora Online.
Additionally ADW support for ONLYOFFICE is provided by https://github.com/atolcd/adf-onlyoffice-extension#installation
Speaker: Darlene Nerden, IBM
Overview: In this session will review the Maximo architecture and factors that influence performance. We will discuss some details for those factors regarding tuning for a performance impact. We will look at troubleshooting tools and Maximo settings to help identify and resolve a Maximo performance issue.
Slides accompanying a day-long introduction to AtoM and Archivematica, presented by Dan Gillean and Justin Simpson at the UK National Archives as part of an AIM25 and Higher Education Archive Programme Network Meeting, December 2, 2016.
MySQL Backup and Security Best PracticesLenz Grimmer
Slides of my talk about MySQL Backup and Security at phpDay in Verona, Italy:
http://www.phpday.it/site/phpday-2009/calendario-conferenze/canale-developers/mysql-backup-and-security-best-practices/
These slides accompanied a presentation by Steve Breker of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see: https://wiki.accesstomemory.org/Community/Camps/SJC2017
These slides introduce users to the Access to Memory codebase. You can find AtoM's code at: https://github.com/artefactual/atom/
Access to Memory (AtoM) is an open source web application for standards-based archival description and access - learn more at:
https://www.accesstomemory.org
These slides will provide users with an overview of how search works in AtoM, along with a detailed walkthrough of using the Advanced search panel, and performing Expert searches in AtoM.
The slides were originally created by Dan Gillean, AtoM Program Manager, for use in a series of training workshops delivered July 9-13, 2018 at the University of the Witswatersrand in Johannesburg, South Africa. The slides are based on current functionality in AtoM release 2.4.
These slides accompanied a presentation by Steve Breker of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
These slides provide advanced users with an overview of AtoM's data model, and demonstrate how a graphical user interface application such as MySQL Workbench can be used to explore the AtoM MySQL database from the back-end. The slides include a number of example queries.
Slides accompanying a presentation delivered at the VII Congresso Nacional de Arquivologia in Fortaleza, Brazil, on October 19th, 2016. The slides provide an overview of the AtoM project's history, its maintenance by Artefactual, and its development philosophy, before proceeding to examine the application as a component used in a digital preservation ecosystem. Aspects of ISO 16363:2012, the Audit and Certification of Trustworthy Digital Repositories standard, are used to evaluate how AtoM can support description, management, administration, and access functions when used to maintain a chain of custody in a trustworthy digital repository ecosystem.
These slides accompanied a presentation by Steve Breker of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
These slides are intended for programmers interested in developing new features for Access to Memory. They first provide an overview of the feature development proccess, and then look at the different types of development typically pursued (plugins, CLI tasks, Background jobs, and core features), with tips and suggestions for each.
These slides were presented by Dan Gillean at the first ever AtoM Camp, held at the SFU Harbour Centre in Vancouver, BC, Canada, March 20-22, 2017. For more information on the Camp, see:
https://wiki.accesstomemory.org/Community/Camps/SFU2017
These slides introduce participants to basic commands in the linux/unix command-line interface, for navigation and basic tasks such as reading, creating, deleting, and moving files. The slides were intended as an initial introduction for archivists unfamiliar with using the command-line, prior to teaching them about the command-line tasks available in Access to Memory (AtoM), which can be used for maintenance and troubleshooting.
Alfresco Content Modelling and Policy BehavioursJ V
Alfresco DevCon 2010 (Paris and New York)
This session starts by giving an overview of components of an Alfresco content model. We then examine the various forms of call-backs and hook-points available to the developer and give some examples of how these can be used to enforce custom business logic and model consistency.
Security DevOps - Free pentesters' time to focus on high-hanging fruits // Ha...Christian Schneider
In this session I will present best practices of how open source tools (used in the DevOps and security communities) can be properly chained together to form a framework that can - as part of an agile software development CI chain - perform automated checking of certain security aspects. This does not remove the requirement for manual pentests, but tries to automate early security feedback to developers. Ultimately the aim is to free pentesters’ time by continuously reducing the amount of
recurring (easy to find) default findings, so that pentesters can use
that time to focus on the really high-hanging fruits.
Based on my experience of applying SecDevOps techniques to projects, I will present the glue steps required on every commit and at nightly builds to achieve different levels of depth in automated security testing during the CI workflow.
I will conclude with a "SecDevOps Maturity Model" of different stages of automated security testing and present concrete examples of how to achieve each stage with open source security tools.
Practical information for Alfresco integration with AOS (Sharepoint Protocol), Google Drive, Microsoft 365, ONLYOFFICE and Collabora Online.
Additionally ADW support for ONLYOFFICE is provided by https://github.com/atolcd/adf-onlyoffice-extension#installation
Speaker: Darlene Nerden, IBM
Overview: In this session will review the Maximo architecture and factors that influence performance. We will discuss some details for those factors regarding tuning for a performance impact. We will look at troubleshooting tools and Maximo settings to help identify and resolve a Maximo performance issue.
Slides accompanying a day-long introduction to AtoM and Archivematica, presented by Dan Gillean and Justin Simpson at the UK National Archives as part of an AIM25 and Higher Education Archive Programme Network Meeting, December 2, 2016.
MySQL Backup and Security Best PracticesLenz Grimmer
Slides of my talk about MySQL Backup and Security at phpDay in Verona, Italy:
http://www.phpday.it/site/phpday-2009/calendario-conferenze/canale-developers/mysql-backup-and-security-best-practices/
Agile PLM's MetaFileRemover ToolIs the file manager space growing significantly in your Agile PLM deployment? Are you using AutoVue? If so, this blog may be just what you’ve been looking for!
Nessa sessão será exposto boas práticas do Amazon Redshift, o dataware da AWS. Tem como intuito de expor de formas efetivas de migração, cargas de dados, realizar tunnings nas suas consultas.
StorageQuery: federated querying on object stores, powered by Alluxio and PrestoAlluxio, Inc.
Alluxio Global Online Meetup
August 25, 2020
For more Alluxio events: https://www.alluxio.io/events/
Speakers:
Abner Ferreira, Simbiose Ventures
Caio Pavanelli, Simbiose Ventures
Bin Fan, Alluxio
Over the last few years, organizations have worked towards the separation of storage and compute for a number of benefits in the areas of cost, data duplication and data latency. Cloud resolves most of these issues but comes to the expense of needing a way to query data on remote storages. Alluxio and Presto are a powerful combination to address the compute problem, which is part of the strategy used by Simbiose Ventures to create a product called StorageQuery - A platform to query files in cloud storages with SQL.
This talk will focus on:
- How Alluxio fits StorageQuery's tech stack;
- Advantages of using Alluxio as a cache layer and its unified filesystem;
- Development of new under file system for Backblaze B2 and fine-grained code documentation;
- ShannonDB remote storage mode.
Drupal Perfomance. Talk given at DrupalCamp North, 25th July 2015.
This session looked at tools you can use to analyse the performance and benchmark a Drupal site. It then looked at tools and techniques that can be used to improve the site performance. The session also included a case study about the Drupal based BAFTA website that was built by Access. Focusing on the recent Film and TV awards, which saw a large amount of traffic in a short amount of time.
Selenium & PHPUnit made easy with Steward (Berlin, April 2017)Ondřej Machulda
Annotated slides from Berlin PHP Usergroup Meetup, 4th April 2017.
---
Not only unit tests but also end-to-end tests in real browser are important part of test automation and test pyramid. So let's have a look how to easily write and run Selenium functional tests using PHPUnit and Steward.
These slides were presented by Dan Gillean, AtoM Program Manager with Artefactual Systems, to provide an update on the AtoM 2.5 release and long-term AtoM3 news to the UK regional AtoM users group meeting held in Glasgow on May 17, 2019. For more information on this group see:
https://wiki.accesstomemory.org/Community/Groups/UK
Fore more information on the AtoM 2.5 release, please see:
https://wiki.accesstomemory.org/Releases/Release_announcements/Release_2.5
Access to Memory (AtoM) is an open source web application for standards-based archival description and access - learn more at:
https://www.accesstomemory.org
To provide users with an easy to install local environment for testing and development, Artefactual maintains a version of AtoM that can be installed on a laptop or home computer, regardless of operating system. We have slides that will explain what Vagrant is and how to install the AtoM Vagrant box here:
http://bit.ly/AtoM-Vagrant
These slides will help users create a re-usable set of data for use in a local AtoM Vagrant environment. Having a set of data that can easily be reloaded will make the AtoM Vagrant box more useful to local testers and developers.
The slides were originally created by Dan Gillean, AtoM Program Manager, for use in a series of training workshops delivered July 9-13, 2018 at the University of the Witswatersrand in Johannesburg, South Africa. The slides are based on current functionality in AtoM release 2.4 - they have been tested in the AtoM 2.4.0.2 and 2.5.0.0 Vagrant boxes.
These slides accompanied a presentation by Dan Gillean and Sara Allain of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
In this session, we looked at the history of the AtoM project, the current governance and maintenance model for AtoM that Artefactual Systems maintains, as well as several other open source business models and stakeholders as we consider ways in which governance and maintenance might look different in the future. Finally, we looked at the state of the application at present with an eye to the future - exploring how changes in international standards and web technologies provide an opportunity to consider what AtoM 3 might look like. The session was followed by open discussion.
These slides accompanied a presentation by Dan Gillean of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
In 2013, with the introduction of AtoM 2.0, Artefactual began a fresh rewrite of all the Access to Memory documentation, using Sphinx Documentation as the primary platform. These slides provide some context and background for this change, introduce Sphinx and reStructuredText, and go on to outline step by step how AtoM users can contribute to the AtoM documentation.
This worksheet accompanied a presentation by Steve Breker of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
The presentation focused on the installation of Access to Memory, and the slides from it can be seen here:
https://www.slideshare.net/accesstomemory/installing-and-upgrading-atom
This handout showed attendees how Ansible can be used to automate the deployment process of AtoM, using the publicly available Ansible playbooks. You can find Artefactual's Ansible playbooks at:
https://github.com/artefactual/deploy-pub
These slides accompanied a presentation by Steve Breker of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see:
https://wiki.accesstomemory.org/Community/Camps/SJC2017
These slides provide developers and system administrators with some suggestions on how to install, maintain, and upgrade Access to Memory. They are intended to supplement the offficial installation documentation, found in the Atom Administrator's Manual:
https://www.accesstomemory.org/docs/latest/
Slides accompanying a day-long AtoM and Archivematica workshop, delivered October 17, 2016 at the VII Congresso Nacional de Arquivologia in Fortaleza, Brazil.
These slides introduce Open Source and Free Software definitions, and proceed to outline Artefactual's approach to open source development and maintenance of the AtoM and Archivematica projects.
Technologie Proche: Imagining the Archival Systems of Tomorrow With the Tools...Artefactual Systems - AtoM
These slides accompanied a June 4th, 2016 presentation made by Dan Gillean of Artefactual Systems at the Association of Canadian Archivists' 2016 Conference in Montreal, QC, Canada.
This presentation aims to examine several existing or emerging computing paradigms, with specific examples, to imagine how they might inform next-generation archival systems to support digital preservation, description, and access. Topics covered include:
- Distributed Version Control and git
- P2P architectures and the BitTorrent protocol
- Linked Open Data and RDF
- Blockchain technology
The session is part of an attempt by the ACA to create interactive "working sessions" at its conferences. Accompanying notes can be found at: http://bit.ly/tech-Proche
Participants were also asked to use the Twitter hashtag of #techProche for online interaction during the session.
Presentation made as part of a community update during Code4Arc, a day-long workshop organized as a part of Code4Lib 2016 in Philadelphia, Monday, March 7 2016.
See:
* http://2016.code4lib.org/
* http://code4lib.org/
* https://www.accesstomemory.org
Project Documentation with Sphinx (or, How I Learned to Stop Worrying and Lov...Artefactual Systems - AtoM
Slides accompanying a lightning talk delivered at BC Code4Lib 2015, held in Vancouver, BC, Canada on November 26-27, 2015.
This talk covered our move from using wikis for project documentation with the Access to Memory (AtoM) project, to using Sphinx documentation with the AtoM 2.0.0 release.
More on AtoM: https://www.accesstomemory.org
More on Sphinx Documentation: http://sphinx-doc.org/
Code4Lib BC: http://wiki.code4lib.org/BC
Introductory slides about Access to Memory (AtoM), accompanying a 4-hour workshop session delivered at the 2015 Digital Library Federation Forum in Vancouver, BC, Canada (see: http://www.diglib.org/forums/2015forum/) on October 28, 2015.
For more information on AtoM, see: https://www.accesstomemory.org
Introducing Binder: A Web-based, Open Source Digital Preservation Management ...Artefactual Systems - AtoM
Binder is a new digital preservation management application developed by Artefactual Systems in conjunction with the Museum of Modern Art (MoMA). This new system aims to facilitate digital collections care, management, and preservation for time-based media and born-digital artworks and is built from integrating functionality of both Archivematica and AtoM.
Artefactual Systems, working with the Museum of Modern Art, has worked to build the first open source digital repository designed to meet the needs and complex digital preservation requirements of museum collections. This new system aims to facilitate digital collections care, management, and preservation for time-based media and born-digital artworks and is built from integrating functionality of both Archivematica and AtoM. This lightning session will introduce the DRMC, outline its design/deployment process, features, and its relevance to archives, libraries, museums, and other cultural heritage institutions undertaking digital preservation.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
4. What do we use these CLI tasks for?
Maintenance
• Installation and upgrades
• Repopulating the search index
• Regenerating derivatives
Import and Export
• Bulk import of XML files
• Importing Authority record CSV files
with Alias and Relationship CSVs
• Using options available in the CLI not
in the user interface
Troubleshooting
• Checking the error logs
• Restarting services
• Trying tasks that resolve common
issues
Doing things quicker
• Deleting large descriptions
• Purging all data
• Promoting a user account to Admin
• Checking your AtoM version
5. Why should I learn this?
Understanding how AtoM
works… and how it breaks
• Some actions in the UI, if they fail,
can be easily resolved with 1 or 2
tasks. Understanding the why and
how will help you use AtoM better
Better communication with IT
• Provide direct suggestions
• Understand what IT is doing
• Shared language
Get better community support
• Provide error logs with Forum posts
• Let us know what you’ve tried
• Save back and forth, get better
responses
Learning the CLI is fun!
• Helps with other applications
• Become more confident on Linux
O/S computers
• Pretend you are a hacker :P
6. Tips for Getting Started
AtoM CLI tasks are run from the root AtoM directory
This means the directory where you have AtoM installed in your current environment.
In production installations – if you have followed our Recommended installation instructions, this is:
> /usr/share/nginx/atom
In the Vagrant box, this is:
> /home/vagrant/atom
7. CLI 101 Reminders
Autocomplete a directory/location/filename > TAB
Show last command > UP ARROW
Abort a process > CTRL+C
Change to a directory > cd <path/to/dir>
Go up one directory > cd ..
Go to home directory > cd
Clear current commands out of view > clear
There are some great cheat sheets and tutorials out there – a simple internet search will uncover many options
8. Tips for Getting Started
> php symfony help <command>
An example of running the help command with the search populate task: php symfony help search:populate
AtoM command-line tasks
generally have help text that
will show the expected syntax,
give a description, and
display the available optional
parameters that can be used
CLI tasks often have
help text built-in
9. Tips for Getting Started
An example of running the help command with digital object
derivative regeneration task:
php symfony help digitalobject:regen-derivatives
Note the 3 options outlined in pink, which you shouldn’t invoke.
The --application,
--env, and --connection
options are part of the
Symfony framework with
which AtoM was built. AtoM
relies on using their defaults to
execute the command-line
tasks properly. Ignore them!
There are 3 options you might see in some commands that
you should not use
10. Tips for Getting Started
Commands are consistently structured
> php symfony type:task --options parameters
• All CLI tools added to AtoM will start with php symfony
• There are several recurring CLI task type namespaces reused
• Examples include tools:, digitalobject:, propel:, csv:, etc.
• The task name tells AtoM what task you actually want to run
• Not all commands have options
• Some options require parameters, such as a filename and path, or other value
• Example: --slug=“the-jane-doe-fonds”
• Example: --alias-file=“/path/to/my/alias-file.csv”
• Not all commands have parameters
• Usually if there is a parameter at the end of a command, it is a path to a file or directory
• Example: bulk EAD XML import command, with the index option used
• php symfony import:bulk --index /vagrant/my-ead-directory/
11. Repopulating the Search Index
> php symfony search:populate
What
AtoM maintains an Elasticsearch search index to
provide fast, full-text search results with faceting.
It is this index that allows AtoM to find and display
records in the user interface when browsing and
searching.
Running this task will delete the current index,
then repopulate and optimize the index.
Depending on the number of records in your
installation, this can take a while to run - for
production sites, we recommend running this task
after regular business hours.
Why
Occasionally it is necessary to repopulate the Elasticsearch
index from the primary database, especially after operations
that affect many records, such as:
• Importing data (CSV or EAD import)
• Adding a new language to the Language menu
• Moving a large series to a new parent record
• Moving a Fonds or Collection to a different archival
institution
• Doing any bulk search and replace operation
• Operations performed in the user interface that time out
AtoM search populate docs: https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/populate-search-index/
12. Repopulating the Search Index
> php symfony search:populate --exclude-types=“informationobject,term”
Using the exclude-types option
Types
• accession
• actor (i.e. authority record)
• aip (indexed during a DIP upload from
Archivematica)
• function
• informationobject (i.e. archival description)
• repository (i.e. archival institution)
• term (such as subjects and places, etc)
> php symfony search:populate --show-types
Keeps the part of the existing index for the listed entities, skipping them (useful if you only need to re-index one type
as it is much quicker). In this example we are skipping archival descriptions and terms (e.g. subjects, places, etc).
Will display the list of available entity types that can be
skipped. You can then either cancel the command to re-
enter it with the --exclude-types option, or
continue to run the task and index all types
13. Clearing the application cache
> php symfony cc
What
The Symfony 1.x framework that AtoM is built upon includes the ability
to cache HTML content, for better responsiveness to HTTP requests.
“One of the ways to speed up an application is to store chunks of generated
HTML code, or even full pages, for future requests. This technique is known as
caching, and it can be managed on the server side and on the client side.
…The principle of HTML caching is simple: Part or all of the HTML code that is
sent to a user upon a request can be reused for a similar request. This HTML
code is stored in a special place (the cache/ folder in symfony), where the front
controller will look for it before executing an action. If a cached version is found,
it is sent without executing the action, thus greatly speeding up the process. If
no cached version is found, the action is executed, and its result (the view) is
stored in the cache folder for future requests.” (from the Symfony docs)
Why
Occasionally, when errors occur or
changes have been made, we need to
flush the cached HTML so we are
being served updated content, and not
an outdated version of a web page.
Running the cache:clear command
will empty out the existing application
cache so it will become repopulated
overtime with updated versions of the
web pages in AtoM that are served to
you.
AtoM cache clear docs: https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/clear-cache/
14. Clearing the application cache
> php symfony cc
Important: there are other caches to clear!
PHP-FPM (a PHP extension that AtoM uses) can also cache some content - if you are clearing the
application cache, you should also consider restarting PHP-FPM (see below, in the “Other maintenance
tasks” slides).
Memcached is also an external cache engine that can be used with AtoM - you should restart it as well.
(see below)
Finally, don’t forget that your web browser has its own cache - in some cases, if you are not seeing
changes take affect, you might want to try clearing your web browser cache. Note that, because AtoM is
session based, clearing the web browser cache might log you out of the application. Be sure you have
any work you are doing in the user interface saved before doing so.
15. Rebuilding the nested set
> php symfony propel:build-nested-set
What
AtoM generally uses a relational database to store its data
(generally, MySQL). However, relational databases, which are
comprised of flat tables, are not particularly suited to handling
hierarchical data.
As developer Mike Hillyer notes, “Hierarchical data has a parent-
child relationship that is not naturally represented in a relational
database table.” One method of addressing this is to employ a
“Nested set model” (Wikipedia).
AtoM makes use of a nested set to manage hierarchical
relationships, such as between parent and child terms and
descriptions.
Why
Sometimes, during operations that involve
updates to large hierarchies, the nested
set can become corrupted - especially if
the server times out during an operation
that reaches the execution limit settings.
This task will rebuild all nested sets in
AtoM, which often resolves issues with
things like the treeview showing duplicate
records, etc.
16. Generating slugs
> php symfony propel:generate-slugs
What
A slug is a word or sequence of words which make up the last part of a
URL in AtoM. It is the part of the URL that uniquely identifies the resource
and often is indicative of the name or title of the page (e.g.: in
www.yourwebpage.com/about, the slug is about). The slug is meant to
provide a unique, human-readable, permanent link to a resource.
Slugs in AtoM are sanitized so the do not contain any special characters or
spaces. Some slugs are arbitrary (like for user account pages), while many
others are based on the record’s name or title (like archival descriptions,
authority records, etc). When a slug is already in use (for example, 2
records named “Correspondence”), AtoM will automatically append a
number to the end of the second slug to make it unique (e.g.
correspondence-2)
Why
In some cases, AtoM may time out in the
middle of an operation that involves the
creation of new records. In such cases, it is
possible that AtoM has died after creating an
information object, but before having a chance
to create a slug for the record. This can cause
unexpected errors in the application - most
notably, 500 errors when trying to access the
records missing slugs through the application
interface. This task will generate new slugs for
any that are missing them in the database.
17. Regenerating all slugs
> php symfony propel:generate-slugs --delete
Generating slugs works for the following entities:
• information objects (e.g. archival descriptions)
• actors (e.g. authority records)
• terms
• physical objects (e.g. storage locations, etc)
• events (e.g. creation events, etc - usually the relationship
between actors and information objects)
• accessions
Note that by default, existing slugs will not be
replaced. If you want to generate new slugs for
existing objects, you will need to first delete the
existing slugs from the database.
This can be useful for records in which a random
slug has been automatically assigned, because the
default user data used to generate the slug has not
been provided (for example, creating an authority
record with no authorized form of name entered).
Using the --delete option will first delete all
exist slugs before regenerating them all.
If an error has left other areas in AtoM without slugs (for
example, a user account’s view page, a donor record, etc),
this task will not resolve the issue - you will likely have to
manually insert a slug into the database for that entity.
18. Regenerating derivatives
> php symfony digitalobject:regen-derivatives
What
When you upload digital objects to AtoM (such as images, audio or video
files, PDFs, etc), AtoM will automatically generate 2 derivative copies for
use in the application: a reference display copy (used on the view page of
a description with a digital object attached), and a thumbnail (for use in
search and browse results, the digital object carousel, etc). The original is
call the master digital object.
When you link to an external digital object on the web instead, AtoM will
generate the local derivatives, but instead of storing the master locally, will
simply point to the web resource.
This command-line task will purge all existing derivatives in AtoM and
regenerate new ones from the master digital objects. It can take a while to
run - for production sites, we recommend running it after business hours.
Why
Sometimes the derivatives will fail to load
(especially during an upload or import that
times out), or you have manually changed
some and want to reset them all. If you are
upgrading from ICA-AtoM, the derivatives are
set to be a different default size, so after an
upgrade, derivatives may appear blurry or
pixelated. Alternatively, if you have changed
the Digital object derivatives settings, you
might want to regenerate your derivatives so
that the new setting is used for multi-page
content such as PDF derivatives.
19. Regenerating derivatives
> php symfony help digitalobject:regen-derivatives
Only regen derivatives for one description > --slug=“<slug>”
Repopulate the search index as the task runs > --index or -i
Force - no yes/no confirmation message first > --force or -f
Only regenerate externally linked objects > --only-externals
Skip ahead and start at a certain filename > --skip-to=“<file>”
Example - force start, index as you proceed, but skip ahead and start at the file silly-rabbit.jpg:
> php symfony digitalobject:regen-derivatives -f -i --skip-to=“silly-rabbit.jpg”
20. Check your AtoM version
> php symfony tools:get-version
What
This simple command will output the version of AtoM you are using (e.g.
2.1; 2.3.1, etc) as well as the current database version (generally a 3
digit number - for example release 2.3 was at database version 138.
Every time new development is added to AtoM that requires changes to
the database, we include a database schema migration to the next
version.
If your database version is incorrect, back up your data, and then you can
try running the sql-upgrade task to migrate to the latest database
schema:
Why
Sometimes when pulling in new changes to
your AtoM instance (for example, updating
your Vagrant box), the database may need to
be migrated to the proper version - this
doesn’t happen automatically(!), and is part of
the upgrade instructions for tarball installations
(from our Downloads page) as well. Knowing
the version can be useful information to share
when seeking support - if it isn’t correct, you
can run the sql-upgrade task to migrate to
the latest database schema. Warning: make
sure you back up your data first!!!
> php symfony tools:upgrade-sql
21. Create an Admin account
> php symfony tools:add-superuser <username>
What
This command will create a new superuser (i.e. an
Administrator account) in AtoM.
The command requires a minimum parameter of the
new username. AtoM will then prompt you for an email
and a new password.
However, you can also pass the email and the password
in a single command as options, as demonstrated below:
Why
If you forget your password and
username, this can be an easy way to get
back into the application - you can then
find your old account and either delete it,
or update the password then delete this
one.
It’s also quicker than using the user
interface to create a new account :)
> php symfony tools:add-superuser --email="email@example.com" --password="MYSUPERPASSWORD" <username>
22. Other maintenance tasks
Restarting services
The following commands will help restart some of the dependencies that AtoM uses. These tasks are not
managed via Symfony or AtoM - instead, they depend on your particular installation environment. The
following instructions assume you have followed our recommended installation instructions - if you have
made changes, some of the commands may be different for you!
Restarting services can be a useful first step in trying to resolve issues - if the service that AtoM uses is in
a bad state as a result of an error that has occurred, then often restarting it can return it to a condition
known to be working.
• Restarting PHP-FPM
• Restarting memcached
• Restarting your webserver
• Restarting the job scheduler
23. Other maintenance tasks
Restarting PHP-FPM
> sudo service php5-fpm restart
On Ubuntu 14.04 (with PHP 5.x)
> sudo systemctl restart php7.0-fpm
On Ubuntu 16.04 (with PHP 7.0)
PHP-FPM is a PHP extension that allows for better
interaction with an application’s web server, via
the use and configuration of FastCGI pools in PHP.
Learn more: https://php-fpm.org/about/
FastCGI is a binary protocol for interfacing
interactive programs with a web server. FastCGI is
a variation on the earlier Common Gateway
Interface (CGI); FastCGI's main aim is to reduce the
overhead associated with interfacing the web
server and CGI programs, allowing a server to
handle more web page requests at once.
From Wikipedia: https://en.wikipedia.org/wiki/FastCGI
24. Other maintenance tasks
Restarting memcached
> sudo service memcached restart
On Ubuntu 14.04 (with PHP 5.x)
> sudo systemctl restart memcached
On Ubuntu 16.04 (with PHP 7.0)
Memcached is an open-source, general
purpose distributed memory object caching
system. It is often used to speed up dynamic
database-driven websites by caching data
and objects in memory to reduce the
number of times an external data source
(such as a database) must be read.
Read more: https://www.memcached.org/
25. Other maintenance tasks
Restarting Nginx
> sudo service nginx restart
On Ubuntu 14.04 (with PHP 5.x)
> sudo systemctl restart nginx
On Ubuntu 16.04 (with PHP 7.0)
Nginx (pronounced “engine x”) is an open
source HTTP web server (among other things).
It manages the interaction between your web
browser and AtoM. Your browser requests a
page in AtoM, and this is sent to Nginx, which
communicates with AtoM to retrieve and serve
the page, or else return an error message.
Learn more:
• http://nginx.org/en/
• https://www.nginx.com/resources/glossary/nginx/
26. Other maintenance tasks
Restarting the job scheduler
AtoM relies a job scheduler in order to execute certain long-
running tasks asynchronously in the background (instead of
synchronously via your web browser, making you wait until the
task is done and the page loaded before continuing), to
guarantee that web requests are handled promptly and work
loads can be distributed across multiple machines.
We use Gearman as our job scheduler in AtoM. “Gearman
provides a generic application framework to farm out work to
other machines or processes that are better suited to do the
work. It allows you to do work in parallel, to load balance
processing, and to call functions between languages.”
Read more: http://gearman.org/
> sudo restart atom-worker
On Ubuntu 14.04 (with PHP 5.x)
> sudo systemctl restart atom-worker
On Ubuntu 16.04 (with PHP 7.0)
AtoM job scheduler docs: https://www.accesstomemory.org/docs/latest/admin-manual/installation/asynchronous-jobs/
27. Other maintenance tasks
Checking the Nginx error logs
If you have encountered an error in AtoM and none of
the previous maintenance tasks have helped to resolve
the issue, it can be useful to get more specific
information from the Nginx error logs.
If you run into a 500 error and want to seek advice and
basic support from the AtoM User Forum, check the
error logs first, and include any relevant error message
with your post - it will help other users better
understand the issue and be able to offer suggestions
on how best to resolve the problem.
> sudo tail -f /var/log/nginx/error.log
AtoM web server log docs: https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/logging/#web-server-logs
Useful when you encounter 500 errors,
to get more information
28. There’s plenty more!
Explore the AtoM documentation and other resources
• AtoM Documentation: https://www.accesstomemory.org/docs/latest/
• AtoM CLI tutorial videos: https://www.youtube.com/playlist?list=PLZiwlG5eSMeyeETe15EsEBSu5htPLK-wm
• AtoM User forum: https://groups.google.com/forum/#!forum/ica-atom-users
• AtoM wiki: https://wiki.accesstomemory.org/
Questions?
info@artefactual.com