I noticed that sources in Rootsfinder have a reference to a repository but it appears to just be a single field entry and is not a link to an actual repository record with all the pertinent information about the repository like it is on Ancestry.com
I see on a Gedcom import you take the information from a REPO record and concatenate it all and dump it in that field which is kind of messy although at least the content isn’t lost. But if something about the repository changed and you wanted to update it there is no way to easily do so across what could be dozens or hundreds of sources.
I have not tested a GEDCOM export from RootsFinder but I’m wondering how that is handled as well, does what was one repository entry on the GEDCOM import become hundreds of REPO records on an export or you just don’t generate any REPO records on an export at all or you try to merge all those repository entries that are exact matches to generate a REPO record?
I’m also wondering if this is because source records in the FamilySearch FamilyTree do not have the concept of a repository for some reason and the Rootsfinder data model was primarily derived or modeled on their API.
Are there plans to actually treat repositories as separate entities at some point in the future? If not is that something you could consider?
It also might be useful to be able to look at a repository and see all the sources in the tree located there, and in turn look at a source and see all the citations/evidences associated with it. But that isn’t nearly as important as being able to properly enter and maintain the data.