Re: [Social-mediagoblin] Tahoe-LAFS as a document-oriented database

[Christopher Allan Webber]

Greg Grossmeier <address@hidden> writes:

> <quoting name="will kahn-greene" date="2011-04-14" time="13:05:16 -0400">
>> To clarify, I don't need all the things a version control system would
>> provide: tags, branching, commit messages, cloning, ...  I just need a
>> list of the previous versions of the image and datetime stamps and the
>> ability to browse the versions as a gallery.
>
> This reminds me of the way F-Spot keeps track of modifications to a photo 
> in its database. Effectively, whenever a modification is made, it makes a 
> new copy of the file, say IMG_1235.jpg -> IMG_1235 (modified).jpg. And 
> then for every new modification it gets a number eg: IMG_1235 
> (modified (2)).jpg.
>
> I don't like how it names the files (the use of spaces and parens) but 
> this style of just listing "modifications" does work well for situations 
> where you only have 1-4 versions of a photo. The software knows that the 
> files created are versions of an original and shows that in the 
> interface.
>
> Greg

This is mostly how things will work in mediagoblin.  The eventual
permanent file naming path we'll choose to keep things unique I'm not
sure of, but we'll be doing things in the patterns described here.  I
think that's good enough for mediagoblin's purposes, especially for now.

-- 
The bottom line.