QR code implementation

45 views
Skip to first unread message

camezq...@gmail.com

unread,
Jul 27, 2017, 11:36:41 PM7/27/17
to AtoM Users
Dear Dan:

Good afternoon from Guatemala. The truth is a long time ago that I had not
written for the amount of work, but the proposal of QR codes in ATOM is as
follows:

In Guatemala, specifically in the Central Archive of RENAP, we have
generated, through the ATOM, an archival description of 95,000 books of
record (old books of civil registry, each book is a file), which is a great
achievement for our institution with your support. Although these 95,000 log
books are described archivistically, we now wish to begin the topographic
inventory.

But we wanted to do something extraordinary, things that many archives would
like to do, and it occurred to us to evaluate the possibility of creating a
QR code for each registry book (that is, a QR code for each file).

What is proposed is that the ATOM generates a QR code for each ATOM
identification code of each file and that the QR code is placed in the
physical book and subsequently that it can be read by a mobile device and
that it is deployed automatically the archival description of the consulted
book.

The other proposal would be to create a QR application in addition to the
ATOM,.

This is a great dream for us, and we would like your help in order to make
this beautiful project viable.

Dan Gillean

unread,
Aug 7, 2017, 10:36:14 AM8/7/17
to ICA-AtoM Users
Hi Cristian, 

Interesting! 

If you proceed with this project, make sure you find an open source library to use that a) is compatible with the languages already in use in AtoM (ideally PHP), b) is compatible with AtoM's A-GPLv3 license, c) is being maintained and not already deprecated. 

After a quick search, I have found one candidate library. I do not know yet if it meets all of the requirements above, but it looks worth investigating. See: 
In terms of development resources, check out these pages on our wiki: 
If you are considering sharing this work back with the public project, I strongly recommend you review the following page: 
The key point to remember is that merging community-generated code is unpaid work for us, that affects how easy it is to maintain the public project going forward. It helps a lot if you a) share early works-in-progress so we can offer suggestions while you still have time budgeted for development, b) follow the guidance of our existing resources c) read the existing code and reuse functions and methods that already exist whenever possible, d) save time at the end for review and changes based on feedback, e) create clean, atomic commits to make it easier for our team to understand what you are doing and review the work in well-contained pieces rather than as a single enormous commit. 

If this is related to physical location/object tracking, then to me it makes more sense to tie such functionality to the Physical storage module, rather than the description view page. Ideally, I would recommend developing this as a plugin, with an on/off configuration in the settings, so users who do not want or need QR codes can disable it. 

We also have some slides that might help you with development. See especially: 

Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056
@accesstomemory

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/34ab1f2c-72bc-4aca-a547-cfd4819400c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages