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

Use subject identifiers instead of eats_id in EATSML #3

Open
ajenhl opened this issue Aug 7, 2012 · 0 comments
Open

Use subject identifiers instead of eats_id in EATSML #3

ajenhl opened this issue Aug 7, 2012 · 0 comments
Assignees

Comments

@ajenhl
Copy link
Owner

ajenhl commented Aug 7, 2012

An issue when importing EATSML from an EATSML export from another system is that the eats_id values are likely to be incorrect, requiring manual merging of the correct ids from the new system into the EATSML. For infrastructural elements, at least, it would be better if the EATSML used subject identifiers and used those to find existing elements in a new system.

Obviously this only works if the two systems have such identifiers in common, but this is at least data that can be managed, where database IDs cannot.

Implementing this change in the EATSML importer and exporter depends on implementing an interface for adding subject identifiers to infrastructure elements (#1).

It might be that in the use case of wanting to merge data from two or more different EATS systems, it is better to just use XTM, if available (#2).

@ghost ghost assigned ajenhl Aug 7, 2012
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

1 participant