![]() I played more this past Saturday and have code to handle the _APID entries and the user media FILE references. Maybe best to not bother with http(s):// support for now for the desktop utility, for Ancestry at least there will always be the wrapper page to obfuscate things. I expect that the media importer will be available January or February of next year (before RootsTech).Įxcellent, thanks much! When the time comes if you need anyone to test please don’t hesitate to drop me an email, I’d love too. I have some DNA features that I’ve committed to implementing in the next couple of months. I anticipate that importing media would be a feature only of the desktop app in order to simplify the RootsFinder site importer. I don’t anticipate that the Import on RootsFinder would support FILE tags with http(s):// references, even if they point to public addresses. If they end up being html pages that need to be parsed, that’s more work and would need to be added later. I’m hoping that those are direct pointers to images so I don’t have to parse the page to get the image url. The thing that needs to be added is support for http(s):// references. I will support both relative and absolute file paths. ![]() Most of the references I’ve seen are for relative paths, without a file:/// prefix. As far as I know, there isn’t a standard format for FILE references. The desktop program will be platform agnostic. Or alternately I could do that and then upload everything to Google drive and refactor the Gedcom to point there and use the Gedcom import on the main RootsFinder site to do the import if it supports it.Ĭurious as to your thoughts, and time frame for the desktop tool you are working on. That would let me consolidate duplicates and perform some other data hygiene tasks at the same time. I could then download the Gedcom, and then parse it and download all the related images both user media and specific media, and then refactor the Gedcom file so this tool you mentioned could be used to upload everything. Maybe it would be better to spend some time cleaning everything up in over the course of several months and creating proper source records for uploaded documents there. Probably 2/3 of those have images I would have to download and upload as well so I am back to thinking about how to best approach that. I know the best thing would likely be to audit my tree and enter everything manually, but I’m increasingly realizing that 20 years of research has produced some 35,000 or so unique source records I would need to enter and that is a huge amount of time. Will this tool support FILE tags with or URIs in addition to local files so it could point to images in Google drive or elsewhere? If so and the Gedcom is from are you going to assume it is not a direct pointer to the image and try to parse the page to get the image URL and then download that? Or it will be able to handle either scenario?įinally, will the Gedcom import on the RootsFinder site itself also support FILE tags with a or URI in them if they point to a publicly accessible resource? ![]() Is there a standard format for FILE references? Are local file references also in URI format or some programs just put absolute or relative pathnames there without the file:/// prefix? If so are you supporting either format? Will this desktop program you mentioned be platform agnostic or Windows only? Not sure what stack you are using behind the scenes but you probably could develop a custom Gedcom importer for Ancestry files that uses Selenium on the back end to login to Ancestry and extract the images during the import… not sure if you guys have worked with it before, it’s a great tool for that stuff when a vendor doesn’t expose a REST or other API to get at stuff. Separate note, but media related, I noticed the Gedcom export from Ancestry has the FILE tags in it for the media items one has uploaded and attached to their tree. It’s basically that idea of being able to export/import the media with everything else… what you are suggesting with a zip format archive is similar and works just as well, and using dropbox or google drive are really great ideas too.Īctually, it’d be nice to be able to add media items by just adding a link to the document in Google drive and either referencing it there or importing it directly from there without a download/upload through the end users machine. ![]() The “portable” format is basically their XML format for the data with the media packaged with it, I think in. My guess would be Gramps is the only thing that supports it at this time although I could be wrong. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |