LEOS multilingual : Services : Import language .leg (reference it to the original proposal)
SUMMARY
On it's current version, LEOS does not support multilinguism for proposals. In order to support such feature, LEOs must be:
- Able to link different proposals under a same context, each of which represents a separate language;
- Able to import different language .leg packages and determine if they represent a new proposal (non existent at all yet in LEOS) or if they represent a language version of an existing proposal in which case they should be linked.
ACCEPTANCE CRITERIAS / GOALS
- Adapt LEOS data model for multi-package support - create a reference table to link packages;
- Adapt the services to the data model changes;
- Create new packages on import .leg keeping original document versioning of the imported .leg - This is a similar to clone proposal logic apart from the versioning part
- Rules for importing .leg of language version:
- Importing the same .leg file without any content change : do not do anything
- Importing the same .leg with changes : creates a newer milestone version based on original proposal milestone version, and we increment from there
- Rules for importing .leg of language version:
OTHER DESCRIPTIONS / DOCUMENTATION