Community development

From AtoM wiki
Revision as of 13:48, 26 November 2017 by Dan (talk | contribs) (→‎eCommerce plugin: Add link for MAID pdf)

Main Page > Community > Community/Community resources > Community/Community resources/Development

In this section of the wiki, we'll add links to custom patches, plugins, themes, images, forks, and other resources developed by community users and publicly available for developers to explore and work with.

Tip

Have you developed custom code for your AtoM installation? Let us know! And... why not consider contributing your code to the public project? That way, we maintain the code for you through future releases, and the entire community benefits from your work! Here are some links to get you started:

CENDARI Shibboleth authentication plugin

CENDARI (Collaborative European Digital Archive Infrastructure) is a research collaboration aimed at integrating digital archives and resources for research on medieval and modern European history. They have chosen AtoM for use as their collaborative Archival Directory (site here, more information here), and have done some custom development, including a plugin to integrate with Shibboleth, an "open-source project that provides Single Sign-On capabilities and allows sites to make informed authorization decisions for individual access of protected online resources in a privacy-preserving manner."

The plugin was developed against AtoM 2.1, and has not yet been tested with other releases. The development was done by Carsten Thiel, primarily between November and December of 2014.

PeaceWorks MAID plugins

In March of 2015, PeaceWorks Technology Solutions helped to launch MAID (Mennonite Archival Image Database), a collaborative project of the Mennonite Historical Society of Canada which includes Mennonite archival partners in British Columbia, Alberta, Saskatchewan, Manitoba, and Ontario, with images held in a shared AtoM instance. Over the course of the 2-year design and development project leading up to the launch, PeaceWorks developed several custom features and plugins for use in MAID, including an eCommerce "shopping cart" plugin for purchasing prints of images available in MAID; an image carousel for the home page; integration with TinyMCE to add a WYSIWYG set of editing tools to AtoM's static pages (e.g. so users did not need to know basic HTML to style static pages); and the ability to upload a different watermark (to be applied to digital object derivatives) for each institution. More details on each below.

eCommerce plugin

This plugin has been developed by Jason Hildebrand of PeaceWorks Technology Solutions, primarily between July 2014 and March 2015.

According to the plugin documentation's Overview section, "This plugin allows website visitors to select and purchase individual photos. Payment for the photos happens via PayPal. E-Commerce admins review each order and may approve or reject (remove) photos from the order. After approval, the customer is sent an email containing a link which they can use to download the image(s).

Users have access to a shopping cart, where photos from multiple repositories can be added as users browse the site, and then ordered/checked out via PayPal. The shopping cart has basic integration with AtoM's PREMIS rights module, so when Dissemination = "Disallow," a message about restrictions is supplied instead. Other features include a vacation setting and a sales report.

MAID has also prepared a summary description of the plugin's functionality, available as a PDF here:

Home page carousel plugin

This plugin has been developed by Jason Hildebrand of PeaceWorks Technology Solutions, primarily between July 2014 and March 2015.

This plugin adds a slideshow to the AtoM front page which displays up to 30 of the most recently added/updated photos in the system. Photos and their captions (if available) are displayed. Users may click a photo to go to its archival description.

TinyMCE visual editor integration for editing static pages

This integration has been developed by Jason Hildebrand of PeaceWorks Technology Solutions, primarily between April 2014 and March 2015. At this time, this integration has not been packaged as a plugin.

TinyMCE is " a platform independent web based Javascript HTML WYSIWYG editor control released as Open Source under LGPL," that, when integrated with AtoM, allows users unfamiliar with HTML to style static pages using familiar buttons, tools, and other user interface elements. The integration includes basic text styling (bold, underline, italics), table creation, image and file upload, link creation, and more.

Per-institution watermarks for digital objects

This integration has been developed by Jason Hildebrand of PeaceWorks Technology Solutions, between July 2014 and March 2015 (primarily in July 2014). At this time, this integration has not been packaged as a plugin.

AtoM includes the little-known ability to apply a watermark to uploaded photos. However there is only provision for a single global watermark which is applied to all images. This customization allows each institution to have their own watermark, and institutional watermarks can be uploaded and managed via the user interface, in the archival institution's "Edit theme" page. Uploading a new watermark will not affect photos already present in AtoM, but AtoM does provide a way for a developer to cause all watermarks to be re-applied (see “Regenerating Derivatives” in the Command-line tools section of the Administrator's Manual of the AtoM documentation for more details).

Docker and AtoM

Two different community developers have combined AtoM with Docker, an open, container-based virtualization platform for distributed applications. Details below.

Tip

Did you know? As of the AtoM 2.3 release, the AtoM project now has its own officially supported Docker Compose development environment! See:

AtoM Docker Files

Created by Dominic Boisvert (@DominicBoisvert) for use in an archival course taught at the University of Montreal, Boisvert has shared Docker files for AtoM 2.1.2, and ICA-AtoM 1.3.2, including simple installation instructions (written in French):

AtoM Docker Compose recipe

Created by John Fink (@jbfink), this is a Docker Compose recipe for AtoM. Compose is described by Docker as "a tool for defining and running multi-container applications with Docker. With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running."

The developer adds, "Note that I've only tested this on 64bit native Linux using Docker directly, so if you're using boot2docker or a VM things might be different." For further configuration information and troubleshooting, see the README provided.

AtoM Docker Image

Created by the Governo Regional Azores, this is a Docker image of AtoM 2.2.0. Note that it does not currently include the MySQL database required for AtoM, which needs to be linked.

AtoM 2.3 ISO image - ready for use on a flash drive

A group of archivists in Brazil, the Grupo de Pesquisa do CNPq GED/A e Patrimônio Documental Arquivístico, have used the SystemBack backup management tool to prepare an ISO image of AtoM 2.3 that can be launched from a flash drive. From the related blog post:

  • Operating System: Ubuntu 16.04 - 64 Bits;
  • Size: 3GBs
  • Format: sblive
  • Remasterer: SystemBack

"After Download, use SystemBack to write to the flash drive, and use with a system boot that is persistent - your data stored in the session will remain available in the next.'"

  • Ubuntu Linux password: icaatom99
  • User in AtoM (ICA-AtoM): GrupoCNPqDocsDigitais@gmail.com
  • Password in AtoM (ICA-AtoM): icaatom

HTML scrub scripts for other entities

Important

UPDATE: Thanks to collaboration among several community members, this work has now been added to the existing AtoM task, and merged into the 2.4 release. For more information, see:

Thank you to Clara Rosales and Darryl Friesen for this collaborative enhancement!

In Release 2.2 we introduced HTML escaping as part of the security enhancements included in the release - the related work is captured in issue ticket #7647. Since some users might have legacy HTML content in their descriptions, we also included a command-line task that would allow users to scrub legacy HTML from archival descriptions - see the related documentation here.

However, this task only currently works for archival descriptions. To help clean up other entities, users from Brazil have adapted versions of the original task that can be run for actors, notes, repository records, and rights records. These were posted in the AtoM user forum on 2017-05-22:

Artefactual has not tested these scripts. To run them:

  1. Download and unzip the rar file attached to the message in the user forum.
  2. Place the scripts in a directory accessible from the root directory of your AtoM instance, such as a new tmp directory.
  3. Use the tools:run command to run each script. For example, for the script to clean up HTML in authority records:
php symfony tools:run tmp/actor_i18n.php

The effects will be similar to what is described for the command-line task:

Retrieved from "http://wiki.accesstomemory.org/index.php?title=Community/Community_resources/Development&oldid=1764"

Account

Page

Search