ADS Harbour was built with the idea that also ADS Classic content would be accessible via this web service also.
Currently, user authentication of ADS2.0 users, and ADS Classic users is done via ADS Classic. In the future, this can be replaced on the relevant backend in harbour. I would suggest a similar idea used for the ADS2.0 libraries, that content is frozen, and stored somewhere in the AWS, for example, a simple SQL database.
Anything else should also be done in a similar fashion, so that older content need not be managed on old systems, but on a new interface, so that any ties to the legacy system are easily cut.
ADS Harbour was built with the idea that also ADS Classic content would be accessible via this web service also.
Currently, user authentication of ADS2.0 users, and ADS Classic users is done via ADS Classic. In the future, this can be replaced on the relevant backend in harbour. I would suggest a similar idea used for the ADS2.0 libraries, that content is frozen, and stored somewhere in the AWS, for example, a simple SQL database.
Anything else should also be done in a similar fashion, so that older content need not be managed on old systems, but on a new interface, so that any ties to the legacy system are easily cut.