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

Suggestions for improving the flexibility of resource containers #202

Open
cckozie opened this issue Dec 29, 2016 · 0 comments
Open

Suggestions for improving the flexibility of resource containers #202

cckozie opened this issue Dec 29, 2016 · 0 comments

Comments

@cckozie
Copy link

cckozie commented Dec 29, 2016

We have generally viewed translation helps (tW, tN, tQ, and sometimes UDB) to be related to a specific ULB. That matches our paradigm for our gateway language strategy, but does not provide for the flexibility that other situations may desire. As an example, there is currently a Russian source that is not a ULB, and given our data structure and the operation of tS, the only way they could get tW, tN, or tQ resources to display in tS would be to designate the source as a ULB. A more flexible way would be to allow the creators of the helps projects to link them to one or more source projects. That would give them the option to create helps that would be linked to a non-ULB source, or even multiple sources if they so desire.

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