I want to code some of this. for now I just want to essentially make some photo album software that can filter photos by who is in them, when they were taken, what type of event they were taken at, etc. I also want to have a family tree view where you can click on someone in the family tree and see all of the photos of them arranged by date/event or something. oh, and I want it to be password protected.
I wanted somewhere to write down the issues I'm having with it so I made this thread.
tentative database structure:
- photos table: id, date, event, person_id, filename
- persons table: id, name
- events table: id, start_date, end_date (these will often be identical.), title, occasion_id
- occasions table: id, name
notes:
- events are specific titles, e.g., "Brian's 2nd Birthday;" occasions are general events, e.g., "birthday."
- should I store photos in the db or on the filesystem? maintaining a nice filesystem organization might suck with a lot of photos that have a lot of different parameters. this might be a case where storing them in the db makes more sense.
- how should I associate people with photos? can I have multiple person_id's? I don't know how this would work. help?
- I might have to tweak the level of info attached to individual photos vs. the event they belong to, because I will inevitably have individual photos that are not part of any event (maybe they could have their own individual event, but that would suck I think.).
- on that not, what should I do with misc. photos? no event_id? then the photos table has to have a date field. hm.
I might start coding this now.
I wanted somewhere to write down the issues I'm having with it so I made this thread.
tentative database structure:
- photos table: id, date, event, person_id, filename
- persons table: id, name
- events table: id, start_date, end_date (these will often be identical.), title, occasion_id
- occasions table: id, name
notes:
- events are specific titles, e.g., "Brian's 2nd Birthday;" occasions are general events, e.g., "birthday."
- should I store photos in the db or on the filesystem? maintaining a nice filesystem organization might suck with a lot of photos that have a lot of different parameters. this might be a case where storing them in the db makes more sense.
- how should I associate people with photos? can I have multiple person_id's? I don't know how this would work. help?
- I might have to tweak the level of info attached to individual photos vs. the event they belong to, because I will inevitably have individual photos that are not part of any event (maybe they could have their own individual event, but that would suck I think.).
- on that not, what should I do with misc. photos? no event_id? then the photos table has to have a date field. hm.
I might start coding this now.
hey one of my family members wanted something like this before too!
christmas / b-day useful wish lists might be useful as well... zomg u need cake pan i haz extras.
maybe synchronize amazon.com book orders and the like...
dunno... myfamilyspacebook?
maybe synchronize amazon.com book orders and the like...
dunno... myfamilyspacebook?
> zomg u need cake pan i haz extras.
:o
:o
Exif data is useful too
what your family doesn't talk like lolcats?
I didn't think of EXIF data. good call, gatzby.