Closed birchamp closed 1 year ago
@mannycolon Here are some tCore storage options for handling orgs:
current example ~/translationCore/resources/en/translationHelps/translationNotes/v33
option 1 - add org to version:
translationNotes
↳ v33_unfoldingWord
↳ v34_test-org
option 2 - add org to resource ID:
translationNotes_unfoldingWord
↳ v33
translationNotes_test-org
↳ v34
option 3 - add org as new layer:
unfoldingWord
↳ translationNotes
↳ v33
test-org
↳ translationNotes
↳ v34~~
moved to https://github.com/unfoldingword/translationcore/issues/7187
I prefer option 1, we do a lot of filesystem calls in our codebase to check for resources and would prefer not to add an additional directory to overcomplicate this process. What do you think?
@PhotoNomad0
Exact match option has been added. (actually it is the default, if you want a partial match, then you use partialMatch=1)
Notes for development:
Need to add to tc-source-content-updater:
Need to do two searches since not all resources in D43-Catalog have been released on DCS.
Then we merge the two lists removing entries in # 2 that are duplicates
Done, back end work not QA testable
What is needed to find the latest releases available for a specific resource type?
Phases:
using CN and just looking at Door43-Catalog results
able to choose organizations
Needed:
Search:
Downloading:
Notes: Explore pivoting on resource type. <= just need to sort by subject type API: https://git.door43.org/api/catalog/swagger#/v5/v5Search
https://git.door43.org/api/catalog/v5/search?subject=Bible%2CAligned%20Bible%2CGreek_New_Testament%2CHebrew_Old_Testament%2CTranslation%20Words%2CTranslation%20Notes%2CTranslation%20Academy&sort=subject&page=1&limit=50
TSV Translation Notes
andTranslation Notes
being returnedTest Assumptions: