Research using the OPDS urls given to us by the Bloom team to get metadata and 'book' files from BloomLibrary
As a reminder, we would not want the URL with our private key to be in anything open source.
notes - next steps to use APIkeys from BloomLibrary in the OPDS interface:
first get it working in a local build with a variable set in Kotlin - don't check in the file that holds the APIkey (use gitignore)
then add a TeamCity build step that gets the alpha or release APIkey from S3 container with the APIkey
possibly have 3 APIkeys from BloomLibrary for debug, alpha, and release builds of SP (for purpose of analytics for each)
- the debug one could be in a file that's available to SIL (& partner?) devs only; debug APIkey could be changed if we are concerned about possible abuse
possible approach using a custom api instead of the OPDS interface
http get to receive a json file of titles available, each item has a url to download it
User Story
As a [choose: local translator / trainer / tech support / admin], I need to __ in order to __.
Is your feature request related to a problem or rationale? Please describe.
Describe specific requirements for what you want to happen : __
Describe alternatives you've considered, and/or additional context: __
The sections above are all that's needed for a request. The following sections are filled out and groomed by the development team before work begins...
To Do:
See the SPEC DOC
In summary:
Acceptance
[steps to verify that the new feature works as expected]
Testing Ideas
[Tips for the testers. If you include detailed steps, use the 'Steps to Reproduce' format (and past tense).]
__
Original Report from __
indented quoted text
is good but optional
Research using the OPDS urls given to us by the Bloom team to get metadata and 'book' files from BloomLibrary
As a reminder, we would not want the URL with our private key to be in anything open source.
notes - next steps to use APIkeys from BloomLibrary in the OPDS interface:
first get it working in a local build with a variable set in Kotlin - don't check in the file that holds the APIkey (use gitignore)
then add a TeamCity build step that gets the alpha or release APIkey from S3 container with the APIkey
possibly have 3 APIkeys from BloomLibrary for debug, alpha, and release builds of SP (for purpose of analytics for each)
possible approach using a custom api instead of the OPDS interface
http get to receive a json file of titles available, each item has a url to download it
User Story
As a [choose: local translator / trainer / tech support / admin], I need to __ in order to __.
Is your feature request related to a problem or rationale? Please describe.
Describe specific requirements for what you want to happen : __
Describe alternatives you've considered, and/or additional context: __
The sections above are all that's needed for a request. The following sections are filled out and groomed by the development team before work begins...
To Do:
See the SPEC DOC
In summary:
Acceptance
[steps to verify that the new feature works as expected]
Testing Ideas
[Tips for the testers. If you include detailed steps, use the 'Steps to Reproduce' format (and past tense).]
__
Original Report from __