introducing 'publish' user preference to set the default for publishing new records
implement frontend caching of preferences
apply the publish preference when importing
added a test for the batch importer to make sure it picks up the publish preference
fixing up some tests broken by the changed behaviour for publish
don't bomb out if there is no current user when asked for defaults
added a publishable mixin to set publish from prefs on create if it's missing
don't cry if something you declared as publishable doesn't have a publish method
explicitly set publish to true on notes in export tests now that it defaults to false via a user preference
now that there is a publish preference extend the privilege of seeing the user prefs menu item to users who can edit archival records
fixing up more broken tests
set memoryleak resource definition ttl to nil for prefs mtime
call super after setting the publish default in create_from_json. and add a test for it.
fixed the fix!
fix the export specs by creating a preference that sets publish to true
removed redundant publish set in import
fix the fix fix. this fix is a slippery fix fish
check that scheme has value before calling match - was blowing up a selenium test