...
Q: What is its current status?
A: Development of the pilot The initial beta development phase came to an end in November, 2014. It is a robust, functioning engine with working APIs, but as a pilot is not being developed further at this time. The code is available at GitHub for anyone who would like to use it. The development team is hopeful that additional funding will let us take it to the next level.Work continues to automate data updates and complete some API development, and LibraryCloud will be reviewed for next steps and further work in March.
Q: What is the relationship of the two LibraryClouds?
A: Ah, so you have heard of the prior version. Excellent! The An earlier, first version was created by the Harvard Library Innovation Lab. The new version, by Harvard Library Technology Services, builds current version builds on that work, and adds a workflow engine to automate its processes. The new version , and is designed to be more scalable and maintainable. The original first version, now renamed lilCloud, serves as a prototyping engine for the new current version.
Q: What is the connection of LibraryCloud and the Digital Public Library of America?
...
A: StackLife is a visual library browser developed by the Harvard Library Innovation Lab. It currently uses the lilCloud API. At , but at some point , we might switch it to the new current LibraryCloud API.
Q: Can I use LibraryCloud for my institution's library?
A: Yes, please! The code is available on GitHub. Of course you’ll likely have to write your own connectors so that you can ingest your data, but please do and share them!
...
Q: What is the status and future of LibraryCloud?
A: LibraryCloud is a pilot projectcurrently in beta release. We hope that it will be implemented and further developed by Harvard Library. In any case, lilCloud will remain operational for the foreseeable future, and the Harvard LibraryCloud code will remain available at GitHub.