Add Barcode Field to Physical Storage

[Tom Misilo]

Hello,

Not sure if this the place to ask for a feature for the current version or if anyone has implemented it themselves.

With the physical storage module is there a way to easily add a "barcode" or identifier field to the physical storage page?

We currently throw the barcode into the Name field, but is not very elegant, and wanted to know what others are doing?

Thanks!

Tom

[Dan Gillean]

Hi Tom, 

There is not currently any Artefactual-led development in this area confirmed to be on the roadmap, and I don't personally currently know of anyone who has shared local customizations adding a barcode field to the storage module. One thing I will say however that might make it easier for a developer to implement such a feature: 

If you look at the two main database tables used in the physical storage module...

[Image from the Entity Relationship Diagrams available on the wiki]

... then you can see that in the physical_object_i18n table, there is already an unused free-text description field. There's currently no corresponding field in the user interface, but one could be added. You'd still need to add the PHP code responsible for handling form submission, and more importantly, you would need to figure out how to add the new field to the search index - but it appears that no database schema migration would be needed to do so. 

This is different than adding a dedicated barcode field AND a description, for example - probably a better long-term solution - but then again, there is a lot that could and should be done in the future to improve the storage module. 

Regards, 

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

@accesstomemory

he / him

--
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-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/cc189027-800b-4c62-a5ff-c69e1e4cea4en%40googlegroups.com.

[Tom Misilo]

Thanks Dan! Is there a preferred method for submitting feature requests for AtoM? I looked on GitHub, but that seems to be more for Bug reports.

Tom

[Dan Gillean]

Hi Tom, 

GitHub is still the best way!

Honestly, things are in a bit of transition right now, and the Maintainers have not yet had a chance to review and update this information, but we do have some general guidelines that I'm pretty sure will still hold up overall on the wiki: 

• https://wiki.accesstomemory.org/Development/Contribute_code
  
• See also: 
• https://wiki.accesstomemory.org/Development/Recommendations
  
• https://wiki.accesstomemory.org/Development/Code_review
  
• https://wiki.accesstomemory.org/Development/Coding_standard
  

A basic summary of important elements: 

• If you haven't previously, please fill out our Contributor's Agreement  (PDF link) and email it to agre...@artefactual.com - we won't review the code until we have one of these! 
• Make sure that your work has been developed against our development branch (qa/2.x) and has been rebased against latest commits to avoid conflicts
• Make sure that you budget time to implement change requests if our Maintainers request them - if we are going to take on the ongoing maintenance of a feature through future releases, then we hope contributors plan to be active in the process, and not just dump some project code on us and expect us to pick it up as-is
• If it's a large feature, our developers will be much more likely to get to it quickly if it's broken up into well-organized atomic commits

Cheers, 

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

@accesstomemory

he / him

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/fc98893e-e4db-41af-9a10-4ae89412e5edn%40googlegroups.com.