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:
Good luck! Let us know how it goes!
Cheers,