User:Ryan52/old todo

kill this page

I need to move all of this page into RT tickets. I've started cleaning it up a little bit.

TODOs

• some changes to the gizmo_events (using a hash, edit buttons, add on submit, etc) should be ported to the contact methods (and other line item types, if not already), if they aren't already
  • add the onsubmit thing for contact_methods as well
  • add the line items edit link for payments and contact methods as well,
  • check the new line item type(s) I've added since then (it was just gizmoes, payments, and contact_methods)
• get tests sane again
  • continuous integration is set up and working, but disabled until the tests work
• add onblur for the automatic line item completion thing (in addition to <TAB>, but only on the last element, I think)
• skedjulnator
  • merging the customizations and defaults
• when editing a return it should link to the sale/disbursement and show a bit of info about that transaction
• cleanup with the prefix in the line item js
• fix our plugins stuff
  • move them to their own git repos
    • submodule them in
  • upgrade to the latest versions
  • forward patches upstream, and hope that they apply the changes
• reports over time:
  • conditions
    • add OR support to conditions ... this will be invasive, probably
• switch to rspec
  • fix existing tests how they are
  • learn to use rspec
  • start writing new tests
• make it work with rails 2.2.2
• interface for adding contracts
• a way to disable contracts
• validation is done on the submit button's onclick...why not the forms onsubmit?
  • important if they submit with the enter button, I think
• covered condition (extra)
  • so we can see either. we don't need side by side numbers at this point, but who knows???
  • maybe a graphing report
• security fixing
  • CSRF (use rails' protect_from_forgery and verify methods)
    • Look at this: [1] looks really kewl!
  • check for SQL injection, we won't have to worry about this in most places since we use active record, but the reports where we use SQL directly should be checked.
  • Rails Security Guide
  • look closer at the XSS stuff (safe erb) -- I got a lot of em
    • the on_display stuff for contact searches is an XSS bug, sort of. regardless, it should be cleaned up.
• remove cruft from that ajax helper thing
  • lots of stuff in app/helpers/application.rb that's probably not used. if it is, it shouldn't be.

library

original list of things needed

• Lookup books from library of congress or similar
• Check out books to people
• Track checkout history
• Print labels
• Inventory list (so we can check to see what's missing, etc.)
• Looking up all overdue books
• (this may not be a complete list)

things left to do

before "beta" test

• integrate the overdue list into a more general list...used to show what a "borrower" has checked out, lost, etc, and used in the overdue list. replace the separate checked out list from overdue list in "member" display.
• redo the labels interface, atm it's not how it should be. and needs support for skipping labels (backend should have it).
• inventory list
• check that the roles are required everywhere they need to be

is this needed?

• search by isbn? right now it's just a text search by title. having problems figuring out how to add more...
• how to handle what to label? currently new copies are added to a list in the session, as well as when you press the button, and removed when you print...this is wrong. we can use store in the database if they've been printed or not, and after you get the PDF you say "yes, it worked, mark them as labeled"...then search for unprinted ones to print.
• labels stuff supports it, just need teh interface. how to do this? we can show X number of tables (depending on how many labels to print) that looks like a label sheet, and have people uncheck the boxes that they want skipped. or just enter the number like it is with the current software.
• what happens after a book is lost?
• does there need to be a publicly accessible

before/during release

• moving from openbiblios schema (figured out)
  • add foreign keys, and create (or redo..) the migrations
  • need to create a temporary rails project that migrates the schema

what I did today

Moved to ChangeLog