User:Ryan52/old todo

plan for returns interface

 * add to the sales/disbursements edit page and receipt to show that something has been returned, and link to the return
 * add a receipt type thing for returns, and also make it general enough to just show the general balance. if the amount changes from a sale (by spending some of the credit), it should also pop up this screen, or add a piece of it to the normal receipt
 * add an interface to transfer store credit from one person to another
 * add a gizmo type to buy store credit (aka gift card type thing, which would then be tzransfered)

features wanted
list of features wanted, most from a discussion with kc8pxy (some will be taken care of by him/his coders), others need my help.


 * settings page (admin password, everything in the defaults table, metadata too..)
 * 01:17 volunteer certification trancking
 * 01:17  aka contact_types? :)
 * 01:18 btu i don't want unilateral  designation.
 * 01:18 i want to have 2 or 3 people to "vote" them competent.

way too old saturday todo list

 * cleanup the data that was deadbeat during the coveredness time. it doesn't have the field set called covered. (fixed in code)
 * add a migration to "UPDATE gizmo_events SET covered = false WHERE covered IS NULL AND donation_id IS NOT NULL"?
 * DELETE FROM gizmo_events WHERE donation_id IS NULL AND sale_id IS NULL AND disbursement_id IS NULL AND recycling_id IS NULL;

i'm working on
LIES! I'm not working on these!


 * library
 * get ticgit ready, and start adding stuff to it
 * port remaining 5 skedjulnator tickets to ticgit (I hope Richard won't mind..)
 * finish sorting trac tickets, and move them to RT or ticgit

for 4/18

 * covered on sales and disbursements
 * finish tweaks (not all, but as much as possible) for library stuff
 * set up "beta" site and email

...

 * add RiFraS's table in a migration
 * and an interface
 * add reports FGdb Reports

later

 * some changes to the gizmo_events (using a hash, edit buttons, add on submit, etc) should be ported to the contact methods and the payments, if they aren't already
 * add the onsubmit thing for contact_methods as well
 * 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
 * skedjulnator
 * make it integrate with the "normal" contacts table and merging the customizations and defaults
 * merge markstos's docs patch

needs discussion

 * "points"
 * returns
 * volunteer scheduling
 * staff hours

blah

 * 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

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)

before "beta" test

 * print labels (mostly done)
 * needs small tweaking wrt the limits on the sides and such
 * 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.

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

later

 * consider regenerating the xapian database on each start up. it might not be that hard on the database. I'll have to time it or something.
 * isbn checksumming

things that matter

 * trac

things that dont

 * gitweb on devo (currently have it on my vps...)
 * lets move everything (mirror, gitweb, devel data, etc) from my vps to oahu instead
 * make the git repos publicly accessible from somewhere other than git.ryan52.info (alternate method is to just make {git,other-dev}.freegeek.org a CNAME to my vps :D)
 * should we also push to github? currently my scripts do pulling, but I guess pushing could be added..
 * rewrite the commit email script -- it sucks (I can live with it now)
 * figure out somewhere for the devel data to live that is faster than the horrible freegeek dsl (heh. I *do* have enough bandwith on my vps...guess I miscalculated or somethin)

should do soonish

 * make it work with rails 2.2.2
 * interface for adding contracts
 * a way to disable contracts

for a rainy day

 * convert the line items junk to use prototype hashes instead of objects
 * review the diffs for nokogiri, keeping in mind the default behavior (// vs /) of the old parser
 * should check back to see differences between the original version of fgss and see if they were intended
 * look through *all* of the xpath and *all* of the xml to look for potential problems
 * add the line items edit link for payments and contact methods as well
 * validation is done on the submit button's onclick...why not the forms onsubmit?
 * add notes via web ui
 * speed up the regex in the vhosting stuff wrt printme, so that it caches results or somethin.
 * coveredness without contracts is broken (in the js) -- no big deal
 * figure out a more convenient way of upgrading to a new sprint
 * covered condition (extra)
 * so we can see either. we don't need side by side numbers at this point, but who knows???
 * update the documentation (meh, not *that* important)
 * security fixing
 * CSRF (use rails' protect_from_forgery and verify methods)
 * Look at this: 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
 * get rid of duplicated data in code
 * permissions for various controllers are split between the sidebar and the controller itself
 * fgss generic regexps
 * 18:44 < aSmig> this should match everything but 31: ([0]{5,}|123456789|^.{1,4}$|^[^0-9]*$)
 * false positives still exist ... figure it out
 * move the vendor/plugins to their own submodules...maybe I shoulda done this first, since it's gonna get even more messy with the git bug...anyway, too late for that, whatever. I'll work it out :)
 * update them

what I did today
Moved to ChangeLog