You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2020. It is now read-only.
I'm not sure quite how we would do this; obviously multiple sources (one per edit) are linked to a person and they often won't make sense without the associated change derived from the versions array.
My feeling is that for importing the candidates into another database you'd want to use the API, as candidates_import_from_live_site does.
Well, I was thinking it can be treated as a bibliography - that's probably better than nothing, right? The two major issues I see are: the sources field being used for things other than sources, as is often the case; and identifying changes that negate a previous change.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The sources are important when importing the candidates into another database, so we might wanna include them in the CSV output.
The text was updated successfully, but these errors were encountered: