transfer archival objects to another repository should reorder their children and regenerate sequences ( otherwise editing will cause errors)
check if the id has already been prefixed
remove parent being returned, which makes moved AO's uneditable
AO transfer to different resources caused problems if they had intances with locations_containers because the dates where converted to strings on the to_json... AND then there's a problem with events leaking the key id into the #relate method, which caused a Sequel error
ooops didnt mean to checkin the mysql connector...
collection management should have a default for the priority and status
spawning a resource shouldn't take certain values from the accession, like collection management, deaccessions, etc
note templates need to be re-rendered on the fly when adding a record via a modal ( otherwise the parent record note template will appear )
bug in FFI