* Source & media naming

[Gary_G]

Helen;

Gary, yes that workflow would be possible. However, are you intending to re-do the fact creation as well? If so, AS would be the way to go [[Nick Walker falls off his chair ]] as it's currently the best option for streamlining creation of sources, linking them to media and creating the facts.

I just ran the new FH 7.0.20 import from RM9. It still has quite a few problems with custom census facts/roles and doesn't generate rich text on import as stated. Not too happy about that. So, I have a choice; check and fix everything or just re-enter all my facts. I'm starting to think the latter is the only robust approach.

[gosforthian]

For all my media files and any other documents I keep, whether inside or outside of FH, my naming structure is always Surname, first names, year of birth and then the document type and possibly its reference. This means I can easily sort and find documents for an individual, which is what I am mostly searching for. People whose trees I have helped with have found this naming sequence to be helpful as well. With an FH project of 28000 individuals the use of surname, first names, year of birth, has not yet produced a duplicate person. Luckily not many Smiths in my tree!
Marriage certs are the problem with this naming convention as there are two people involved and I have to choose one of the people to be named first. I always choose the person who is a relative first and the "incomer" second. I have never included the date of the event in the document name, not sure why, I suppose because it is already in the FH database. Examples are:

Ackinclose, George Edward, 1967, and Stainback, Michelle Ann, 1968, marriage cert
Ackinclose, James Albert, 1919, photo thumbnail obit
Ackinclose, Garret, 1882, Census 1910 USC_1910_004973803_00599
Gilroy, Hugh 1883, WW1 Service record p1

Hope this helps
Ian

[Little.auk]

I take care to give a source and associated media file(s) the same name (Source short title, media file name) may be with a (1 of x) appended for media files if there are multiple images making up the source.

I do the same, for similar reasons, and also because media files are often collected a little time before being added to FH. Therefore I find it helpful to give media files descriptive names when I first save them - as per the census image example -

Census 1861 (IM) PARTRIDGE James - Dinah (SAMPSON) [F0046-0000].jpg

(IM) identifies a census page image - I use other identifiers like (TR) for transcript - (PR) for parish record and (GR) for GRO certificates.
For censuses I use the 'Head of Household' name - plus spouse (if recorded). The final entry is the Custom I.D. - (prefixed 'F' for family or 'A' for individual).

I find that, in most cases, I am working on events which is why these come first. I also have some quite large families in my tree, so census images (sources) applying to 8 to 10 individuals are not uncommon!

Just to add - I use AS, which is excellent for creating these sources.

[TinaS]

This thread has been an interesting read, and I am surprised that I handle media in a totally different way - must be my scientific research background.

I name my media files according to the original source, just as I used to name my personal transcription notes when visiting public libraries to trawl through micro-fiche back in the day. Here is a fictional example:

if it is a snip of a specific marriage in a parish register:
hampshire cove stjohn marriages 1870-1920 p23 n56

if it is page(s) of baptisms:
hampshire cove stjohn baptisms 1870-1920 p22-23

if it is a census:
rg13 1104 54 1

These media files are linked to the sources (I am a splitter) and hence the person via the fact they are sources for. I use the genealogy software to pull out the relevant media for an individual. This method ensures that I capture the essential source data with the image so that I know exactly where it is from when it is later used to create a source record.

I guess it all depends on your workflow and the ways you need to access/use your media, and what works for you.