Go to file
voussoir 1784e584e2 Don't let Bookmark.edit with a blank url. 2017-07-13 22:58:02 -07:00
etiquette Don't let Bookmark.edit with a blank url. 2017-07-13 22:58:02 -07:00
frontends Include an extra, more general css class "editor_button". 2017-07-09 19:51:58 -07:00
tests Move tests to tests folder (even though they're empty...) 2017-05-01 21:50:23 -07:00
utilities Give Tags a description field. 2017-05-12 17:31:17 -07:00
.gitignore checkpoint 2016-09-18 01:33:46 -07:00
LICENSE.txt Apply BSD 2-Clause License 2017-03-17 02:48:11 -07:00
README.md Add more stuff to the to-do list. 2017-07-09 15:48:47 -07:00
requirements.txt checkpoint 2017-01-06 18:08:22 -08:00

README.md

Etiquette

I am currently running a demonstration copy of Etiquette at http://etiquette.voussoir.net where you can browse around. This is not yet permanent.

What am I looking at

Etiquette is a tag-based file organization system with a web front-end.

Documentation is still a work in progress. In general, I use:

  • python etiquette_flask_launch.py [port] to launch the flask server. Port defaults to 5000 if not provided.
  • python -i etiquette_repl.py to launch the Python interpreter with the PhotoDB pre-loaded into a variable called P. Try things like P.new_photo or P.digest_directory.

To do list

  • Make the wording between "new", "create", "add"; and "remove", "delete" more consistent.
  • User account system, permission levels, private pages.
  • Improve the "tags on this page" list. Maybe add separate buttons for must/may/forbid on each.
  • Some way for the database to re-identify a file that was moved / renamed (lost & found). Maybe file hash of the first few mb is good enough.
  • Debate whether the UserMixin.login method should accept usernames or I should standardize the usage of IDs only internally.
  • Ability to access user photos by user's ID, not just username.
  • Should album size be cached on disk?
  • Replace columns like area, ratio, bitrate by using expression indices or views (width * height etc).
  • Add some way to support large image albums without flooding the search results. Considering a "hidden" property so that a handful of representative images can appear in the search results, and the rest can be found on the actual Album page.
  • Add a Photo.merge to combine duplicate entries.
  • Generate thumbnails for vector files.
  • Allow photos to have nonstandard, orderby-able properties like "release year".
  • Make the FFmpeg path configurable. Some kind of global config? Or part of the database config file?

Changelog

  • [addition] A new feature was added.
  • [bugfix] Incorrect behavior was fixed.
  • [change] An existing feature was slightly modified or parameters were renamed.
  • [cleanup] Code was improved, comments were added, or other changes with minor impact on the interface.
  • [removal] An old feature was removed.