Peter Bienstman wrote:
>> The main one being that anki
>> imports and renames image files that you may wish to use in your cards
>> and holds them in a flat folder structure. I don't want to do that. I
>> deliberately rename jpegs to have meaningful names and contain useful
>> exif data and resized to suit mnemosyne. I also use the same jpegs
>> linked to from an openoffice database I'm working on which simply links
>> to the same physical files. And sometimes I use the same jpeg in several
>> mnemosyne cards depending on my goals.
>>
>
> Note that 2.0 currently makes a copy of your picture files and stores it in
> its
> own folder (it does not rename the files though, so they can still have
> meaningful names).
>
> The idea behind is that that makes it easier for users to backup their cards
> +
> media files if they are all in the same place.
>
> I'm open for discussion on this, though.
>
Where does it store this folder and would it be user configurable? How
would it cope with, say, several thousand images in one folder?
I experimented quite a bit early on with image housekeeping and
management as I know it's going to be a substantial part of my card
database and have quite a simple system that works fine for me at the
moment. Under my .mnemosyne folder I have an images folder. In the
images folder I have all the genera for things I wish to learn. So
typically:
~/.mnemosyne/images/Betula
will contain all my ident images for Birch species.
This is working out quite nice and elegantly for the moment as it should
scale up quite nicely as I add images. Currently I have 160 image files
in about 60 folders but expect this to scale rapidly. My naming system
is consistent so, in due course, I can use the same images in a database
I want to create in OpenOffice. oobase 3.1 allows direct (relative)
linking to images so making efficient use of disk space.
Furthermore I use nfs to export my .mnemosyne folder to any Pc on my LAN
so I can run mnemosyne (using -d) on any PC (although Vista moans) and
use the same card database and keep my learning consistent.
Backing up is easy. I use a wrapper script to invoke mnemosyne so I
don't forget, but basically it simply backs up the entire .mnemosyne
folder to another location, where it can later be copied to removable
media or another PC. I use rsync ( http://www.samba.org/rsync/ ) for the
backups which only copies updated files so it is very quick.
Dougie
--
You received this message because you are subscribed to the Google Groups
"mnemosyne-proj-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mnemosyne-proj-users?hl=.
