Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature suggestion : sources #59

Open
raphink opened this issue Mar 1, 2017 · 5 comments
Open

Feature suggestion : sources #59

raphink opened this issue Mar 1, 2017 · 5 comments

Comments

@raphink
Copy link
Contributor

raphink commented Mar 1, 2017

Currently SmartCopy can add URL references to the about section of profiles.

It would be even better if it could add a document with the URL and tag sources in it for all the data imported from the URL.

@raphink
Copy link
Contributor Author

raphink commented Mar 1, 2017

This would document imports even better and would allow to see exactly what info was imported from a given URL. Ideally, SmartCopy would find existing documents with the same URL if they exist.

@raphink
Copy link
Contributor Author

raphink commented Mar 1, 2017

Another option could be for Geni to expose the Matches API so we can add these URLs as matches, although that in itself will not document the sources (which I still believe would be useful).

@eljeffeg
Copy link
Owner

eljeffeg commented Mar 2, 2017

Yeah - It would be nice if we could add it as a match and it would be nice if we could link sources to matches. But I would only be interested in linking sources to record matches, not trees. Same goes for documents. I don't see online trees as a sources themselves, though the online tree could reference sources. I would only want to add a source if it referenced actual documents or authorities.

@eljeffeg
Copy link
Owner

eljeffeg commented Mar 2, 2017

I've asked in the past for access to the Match stuff, but it's integrated with MyHeritage. Not sure how complicated that would be for them based on the various sites SC may use.

@raphink
Copy link
Contributor Author

raphink commented Mar 2, 2017

I see. I agree about the sources. Sources are supposed to be dated and localized, so it doesn't make sense to use a tree for that. But it could make sense to use that for cemetery websites and such, or even archive ones.

As for matches, there could be lots of use cases, e.g. Wikipedia articles, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants