I’m on RM 11 with my media folder set to \public\Pictures and data folder to \public\Documents. I always use “Drop New Media” and I never enter captions. I only sync to Ancestry and FamilySearch (no merges into RM).
I just found two people with duplicated media in a folder that RM created under my data folder, named TreeName_media. The duplicates in that folder have captions that are simply the first ~70 characters of the file name. The original files in \public\Pictures still look normal and have no captions.
Has anyone seen RM 11 (a) create a TreeName_media folder under the data folder and (b) auto‑generate captions from the filename like this? I’ve added thousands of images and this is the first time I’ve seen it. Any idea what could trigger RM to do this for just a couple of files?
TreeName_media was created automatically when you downloaded the Treename from A*. The duplicates were downloaded from A* at a later time due to some action being taken on A* which flagged them as new media and they came down during a Treeshare session.
To follow up on the answer from bobc, you must have merged from Ancestry into RM at least once using TreeShare, perhaps by accident. That’s the only way media files are placed into the TreeName_media folder.
Even if you have a folder configured for media, RM will create a folder in the data folder for media? I am very careful both in TreeShare and Family Search not to bring intentionally bring data in from the internet. If the consensus is that is the only way this could happen, then I’ll accept it.
Since there are two distinct sides in TreeShare, the only time I select anything on (from?) Ancestry is to delete information that I removed from RM. By selecting anything on the Ancestry side, could that do it?
Yes, everything that TreeShare brings in for you does it’s own thing. It names the file with a meaningless name. It stores the file in TreeName_media no matter what you setting is for the default media file.
Indeed, it’s worth reiterating that the default media file that you set via Settings > Folders > Media folder never tells RM where to store any of your media files. If you are linking files into RM yourself rather than having TreeShare do it for you, there is a sense in which Settings > Folders > Media folder is almost irrelevant. It does have relevance as follows.
If you link media files into RM via Add New Media, Settings > Folders > Media folder determines which folder RM opens so that you can pick the file to add. But you still can and often need to navigate to where the file really is, for example if you have a large subfolder structure. If instead you use Drop New Media, then Settings > Folders > Media folder is irrelevant for navigating to the proper folder. Instead, you are totally responsible for that yourself.
Beginning with RM8 and continuing on through RM11, RM stores the path to media files via what are called relative media links. Such links are relative to the Settings > Folders > Media folder if possible. This feature is primarily of benefit to users who are running RM on two computers and where their media folder is not in the same location on the two computers. If a media file is not within Settings > Folders > Media folder, then it stores the path of the file relative to the computer’s Documents folder. And if that’s not possible, it stores the path of the file relative to the root of the C: drive, just as RM7 did for all files.
I always like your responses because it helps me sort through my issues/concerns and you don’t mind when if I question something you say. As a programmer myself, I understand that folder settings within a program is not “telling” the application where to store items. Also, RM does not store the actual path in the multimedia table. My thinking was only that RM would reference that if you were to download media. Now, I realize that my thinking was flawed, and it also explains why there were captions; TreeShare does its own thing.
One item to note which is also what bothered me which I should have noted, the file name under the treename_media used the same naming standard that I do. I should have mentioned that because I would have expected TreeShare to use its own naming convention also. You just helped me realize that.
so in theory – the media would seem to have been in the media Gallery in order to comeback into RM with a caption? And if the same filename was on both sides that is possible it could cause a duplicate mediaID because it was in diff paths? (even if same filename)
My filenames are standards which I created: Lastname, First name(birth-death) - [source type] year place. There is no way TreeShare would have created that and I never use captions. Both files which were duplicate had that format for a name and added the first 70 characters as a caption.
Jerry’s response made me realize I should have included that in the first post. One of the reasons I don’t download media (intentionally) from Ancestry is because I also use the filename for my Citation Name. I am fully aware that TreeShare has its own naming convention. That was the other reason I decided to post the question.
By chance do you have any media in your Media Gallery online Ancestry? and by chance were of the media the same MediaNames (as ones you had issues with)
Yes, I do have media in the Media Gallery online and the do have the same name as my files.
Things just got interesting! Because it has been a couple of months now since the duplication happened, I don’t have any background or timeline. Maybe it’s not TreeShare that comes up with obscured names, but Ancestry instead. It would make sense that Ancestry would have their own naming convention and TreeShare pulls the file, downloads it and adds the filename as a caption. It would also mean that at some point, I used TreeShare to send the source with the media to Ancestry and Ancestry kept my filename.
New question becomes, if TreeShare sends new data from RM to ANC, why would TreeShare send that back to RM.? Meaning, the information should be in Sync if they are identical.
This, now, adds to a list of weird issues I’ve had with TS but didn’t want to bring up.