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.

Sign up for GitHub

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

Jump to bottom

Propagate default mappings from target app #2

Open
rob-metalinkage opened this issue May 4, 2016 · 2 comments
Open

Propagate default mappings from target app #2

rob-metalinkage opened this issue May 4, 2016 · 2 comments
Labels
enhancement

Comments

@rob-metalinkage
Copy link
Owner

Allow an app such as skosxl to define default mappings (to SKOS!) and have these used by serialiser automatically.
@rob-metalinkage
Copy link
Owner Author

Must also initialise this post_save signals and load reasoning rules (and ontology dependencies) to remote store

@rob-metalinkage
Copy link
Owner Author

Djangos loaddata and migrations seem to be not designed for this purpose - migrations are possible to hack - but just very nasty to try to persist in git without mixing up with autogenerated ones - seems to be designed for one-off data migration be experts, not automated setup. (django not so happy with data-driven functionality)

also not easy to see how to override defaults.

currently writing init endpoints that use ORM directly to get an idempotent initialisation to meet downstream module requirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rob-metalinkage