Family Historian User Group

Personally, I don't split the Media folder according to family branches, because as your family tree grows you may well discover other branches and then it starts getting complicated to decide which media belongs in which folder.
Also, it is quite common to discover that two initially separate branches share a common ancestor, which merges them together, so which folder do those ancestors belong to?

Furthermore, it is rarely necessary to know exactly where the Media files are stored, because you usually operate with them via FH and AS. The Media are linked via Media records to the Individual and Source records, which is where you usually encounter them. The search tools in FH and AS allow the Media to be located without knowing where they are stored in the Media sub-folders.

However, if you wish to rearrange your Media sub-folders for any purpose there is a strategy.
See how_to:changing_external_file_links|> Changing External File Links for advice.
In summary, first use Windows File Explorer to rearrange all your Media sub-folders and move the files where required, but do not rename any of the files.
Then in FH use Tools > External File Links and the Auto Repair Links button, which should correct the Media record File links to the new sub-folder paths.
If that does not work then the Re-Map and Edit buttons can perform the changes as explained via the Help button advice.

OK, it is reasonable to stick with your Birth, Death, Census structure of sub-folders.
See how_to:organise_your_files|> Organise Your Files for ideas.

You mention AS and while discussing Media naming, it's worth reviewing the Templates in AS for naming Sources and Media.
See ancestralsources:index|> Ancestral Sources tutorials on Working with Options and Working with Templates.

But be aware the Windows has a maximum path length of 260 characters eg:

C:\Users\Paula\Documents\Family Historian Projects\John R. Piper Family Project\John R. Piper Family Project.fh_data\Media\

is a path length of 123 characters, and this is without a file name. If you end up with path lengths of more than 260 some programs will fail.

Note (from a Microsoft web page):
"Starting in Windows 10, version 1607, MAX_PATH limitations have been removed from common Win32 file and directory functions. However, you must opt-in to the new behavior."
Opting in means making a change in the Windows registry - a no no unless you really know what you're doing!

Thank you David, but that is covered at some length in how_to:organise_your_files|> Organise Your Files.

I didn't know about the change in Long path names in Windows 10. Good to know. I have found an article about it with instructions at

https://www.howtogeek.com/266621/how-to ... haracters/

If you are uncomfortable accessing the Registry there is a link - Long Path Names Hacks - within the article containing a zip file with two .reg files which allow you to perform the edit without opening Regedit yourself.

David

Yes David, but did you see the warning?
"There is one caveat. This new setting won’t necessarily work with every application out there, but it will work with most."
So even after the Windows Registry hack you may still experience the problem with some programs.

I did read the caveat and it is possible that FH is one of the older 32-bit programs which cannot open or save very long path name files - I don't know. I was not recommending the use of a registry hack simply pointing out for interested parties where it can be found.

David