TODO for Launch

I have tried to pin down what would be a showstopper until Centrifuge can be made public, or to be more precise: What will not work for any entity that is not the CMC.

  • Barcode printing: This is currently done with kbarcode at the CMC. This dependency needs to go but I have no clue yet, how to get images of barcodes into the fpdf template, or if that is even possible.
  • Labels in general: Avery 5160 are hardcoded, this is hardly desirable, but the question remains how to format the outputted text to match *any* given label without adding overhead the size of the whole current application for that.
  • Backup (or file transfer/download in general): "It works" but the implementation is sub-par, if not outright dangerous. Triggers nice save as download.
  • Access Control: We currently use plain .htaccess permissions, which are easy and simple for an administrator but not as easy to figure out or as fine grained as an end user might prefer. I might append the application with standard PHP authentication but I'm hardly informed about the security problems with that approach and need to dive into a sufficient amount of documentation first.

I intend to update this article once a certain problem is solved or a new one creeps up to keep track of the current state of affairs.

posts: