CVS edit link for Nathaniel

I originally started building this module to fulfill a need in my current office management position for a small business. They have a parts room with hundreds of parts and no way to track anything. Just over a year ago the business didn’t even have an Internet connection. Anyway, I built a database with drupal and created barcode_listener and barcode_inventory. These two modules work together to listen for a barcode scanner that is connected to the computer via usb (or other) and record the data entered for the corresponding part (node). There are several uses for a module like this. It works well with the barcode cck module. Use that module to create and print labels, then use the two modules here to track whether that item is checked in / out or how many are in stock etc. Ideally barcode_listener should be an API that integrates with other custom modules and listens for the scanner then triggers some action.

This module might be useful for a stock room or small classroom to check out items / books / tools etc.

I would like to offer my work back to the community and hopefully receive some feedback and enhance the module to meet other needs. barcode_inventory integrates with the views module to display a history of actions (op i.e. in / out, date, user, # of items per transaction). It also tracks total number of items in stock and hooks into the node form for the type selected in the barcode inventory settings page if the stock for that item needs to be updated manually (because not everyone uses the scanner... all the time)

On the settings page for barcode_listener: set up one character for the header, also known as the preamble, (set up your bar code scanner to lead with one odd character that is not found in any of your barcodes, default is “}”), there is also an advanced option to edit the javascript function directly (default code is provided in the readme file). On the settings page for barcode_inventory: select one content type that is associated with barcodes, select field(s) associated with barcodes (cck, barcode, and/or title).

A menu item is added with barcode_inventory called Barcode Listener default tab “Inventory” other tabs: “Check In” & “Check Out”. On the inventory page you can scan a barcode or enter the code manually. The module will check if the code is associated with a node, if not, suggest creating a new one, if yes, display how many are in stock and last 10 scans.

CommentFileSizeAuthor
#1 barcode_listener.zip12.65 KBnathaniel

Comments

nathaniel’s picture

nathaniel commented
Component: Miscellaneous » miscellaneous
Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new barcode_listener.zip12.65 KB
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Component: miscellaneous » new project application
Status: Needs review » Needs work
Issue tags: +Module review

Hello, and thank you for applying for a CVS account. I am adding the review tags, and some volunteers will review the code, pointing out what it needs to be changed.

I will report here a little checklist:

  • The code needs to follow the coding standards; check in particular the format used for the control structures, and the name given to PHP variables, Drupal persistent variables, functions defined from the module.
  • Files available from third-party sites should not be included within the module/theme. This is particularly true for files that are not licensed under GPL License v2, but it is also true for files that are licensed under the same license used by Drupal.
  • The license file should not be included as well; the packaging script already include that file. In any cases, the code for modules/themes committed in drupal.org repository needs to be released under the same license used by Drupal; any compatible license is not allowed.
  • Check the code passes the Coder validation.

As per requirements, the motivation message should include more than two sentences (the exact words are a few paragraphs) that describe the module features. For themes, it should include also a screenshot of the theme (at least 640x400 pixels), and (when possible) a link to a working demo site; for modules, it should include also a comparison with the existing solutions.

zzolo’s picture

zzolo commented
Status: Needs work » Postponed

Hi. Please read all the following and the links provided as this is very important information about your CVS Application:

Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:
Migrating from CVS Applications to (Git) Full Project Applications

  • The status of this application will be put to "postponed" and by following the instructions in the above link, you will be able to reopen it.
  • Or if your application has been "needs work" for more than 5 weeks, your application will be marked as "closed (won't fix)". You can still reopen it, by reading the instructions above.
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes
Status: Postponed » Closed (won't fix)

As per previous comment, I am setting this issue to won't fix.

Since new users can now create full projects, applications have a different purpose and they are handled on a different issue queue. See Apply for permission to opt into security advisory coverage for more information.