Hello, Library users and contributors! We have some details about an upcoming conference session to share with you, as well as some new features.
Communication
We’re excited to see some new faces on Github, with four first-time contributors committing code in the past few weeks. Issues remain a great place to talk about how we hope to evolve the platform.
The #proj-library slack channel in News Nerdery is a great place for discussing and getting help with Library. If you’re not part of NN, sign up with your organization’s email.
Finally, be sure to join our Google Group to receive news and updates from the maintainers. The group is also a great place to start discussion about potential new features or squashing bugs.
How are you using Library? We’d love to hear from you.
NICAR 2020
We’re excited to announce that we’ll be presenting Library during a Friday morning commons presentation at NICAR 2020. If members of your organization are attending and interested in learning more about Library, we encourage you to stop by the session!
What’s New
- Timestamp changes: Documents now show a relative creation time, and will show absolute dates by hovering over the relative timestamps (#84). A bug regarding timestamps in search results was also fixed (#86).
- Cache rewrite: Library’s caching logic was significantly simplified, modifying the way parsed document data is stored. We hope this change will remove most unexpected behavior caused by over-aggressive caching (#92).
What’s Next
- Documentation updates: some of our documentation for setting up library has confused newcomers, and should clearly distinguish developer and production set-up procedures. (#85)
- Folder-based instance improvements: Library’s code paths for shared folder and shared drive-backed instances slightly differ due to API differences. We’re continuing to investigate possible folder bugs, and improvements like API response partitioning (#87) will ensure Library remains scalable and performant regardless of the backend.
- DX and Onboarding Improvements: We’re cleaning up logging and error handling logic for clearer guidance on nonfatal errors and suggestions to resolve common snags. (Onboarding Improvements)
What would you like to see next?
We’re thrilled to see so many feature requests on GitHub, and look forward to hearing more about what changes would be most valuable to you and your organizations.
Feel free to reply to this thread, message us on Slack, or submit an issue on GitHub with any suggestions.