Re: [Gramps-devel] Proposal for default media directory

[Doug B. <dou...@gm...>]

On Tue, May 15, 2012 at 4:39 PM, Nick Hall <nic...@ho...> wrote:
> Doug,
>
> I have a few comments and questions.

Sure. Note that I really only have need for one of the following, but
this discussion is useful for future uses.

> On 13/05/12 13:45, Doug Blank wrote:
>>
>> So, here is an amended proposal:
>>
>> 1) Move the default media path to the database. This will require it
>> to be stored in XML, and on disk. There are two bits of text
>> associated with a database: bdbversion.txt and name.txt. We could
>> combine all text into a single file (xml or ini). Or we could create a
>> third text file. (If we create an xml/ini file for the database, I
>> could think of other things that could go there, BTW.)
>
>
> As you already pointed out the relative media path is already stored in the
> database.
>
>
>>
>> 2) Should we change the name from "relative media path" to "default
>> media directory"? Tools for changing the path would describe it as
>> being "relative to the default media directory".
>
>
> Yes, we could improve on the description.  Perhaps just "Media directory"
> would be clear to most users.

Sounds good.

>>
>> 3) Media dropped onto Gramps will be copied to this directory. (Could
>> have a popup allowing a choice as well.)
>
> I don't like this idea.  Gramps media objects are links to media, not the
> media itself.  Dropping media onto Gramps should create a media object (a
> link to the media), not move or copy the file itself.

Not all media comes from the file system, but may exist only in a
clipboard or in a drag and drop. For example, it may be that you want
to drag an image from a web browser onto the gramps gtk window. But I
agree that some thought should be given to this, and may require a
popup in any event.

> I would expect a media directory to contain a hierarchy of directories to
> organise the media in an effective manner.  When putting new media into
> Gramps the user will want to copy the file to an appropriate location and
> then create a media object (a link to it).
>
>>
>> 4) Add tool to allow moving of media to this default media folder.
>
>
> I'm not sure that I understand this.  Where would I be moving the media
> from?

In the use-case I am thinking about, I would like to recombine media
that has been worked on a different computer, exported as packaged
XML, and then moved to a new system. Having all of the media in a
single folder might be a useful option. Or maybe moving the relative
paths to a root would be useful too.

> Suppose I receive some new media, that I want to put into Gramps.  At the
> moment I need to perform two steps.  (1) Move the files into a directory in
> the media structure (not necessarily the root).  (2) Create a media object
> for each file.
>
> Are you trying to simplify this process?

Yes.

>>
>> 5) Web imports would put incoming media here.
>
>
> Yes.  OK.

This is my main goal for the moment.

>>
>> 6) For new databases and imports that don't store the relative media
>> path, should we set the initial value to the current value, ie user's
>> home? That will keep the current meaning working as it currently does.
>> (The web import would have a different initial value.)
>
>
> A default value seems sensible.
>
>
>>
>> 7) In addition to adding ${user} and ${grampshome} variables to be
>> used in this path, we could also include ${database} for allowing
>> media based on the gramps database folder, eg
>> /home/user/.gramps/user/45234.
>
>
> The idea of a ${database} variable is interesting.  I can see why you might
> want to store media files with a database.  Would these be copies of files
> stored elsewhere?

Not necessarily. But I am thinking about how to migrate/merge media
files from Gramps-gtk to a file server, and then back.

> Would the files be stored in a single directory, or would a hierarchical
> structure be maintained?  If we used a single directory, how would we deal
> with duplicate filenames?  Would we rename files based on the media handle
> for example?  Are you proposing creating a sort of Gramps repository for
> media files?

Just trying to make some better media options. Thanks!

-Doug

>
> Nick.
>
>> -Doug
>>
>