- We’ve just created a listserv, email@example.com. We will use the listserv to communicate with Merritt users, particularly with information about scheduled or unscheduled maintenances. We’ve added many people already working with Merritt (and you’ll have received a notification from the listserv if you’ve been added). If you’d like to be added to the listserv, please contact us at firstname.lastname@example.org.
- As a follow-up to the UC3 workshops in November, we are working on a Roadmap listing our priorities for Merritt. The Roadmap will list the software development we will be working on in the coming 12-18 months. Look for the Roadmap in February.
- We implemented a new version of Inventory in response to the problems we were experiencing in the fall. Inventory is the micro-service that stores metadata about the content in Merritt, and provides those metadata records to the user interface when needed for display and reporting. The original Inventory used 4Store to store the records, but it did not provide the level of performance we needed. We have just switched to MySql, and are finding that the performance is much better. We’re seeing much faster response times in many of the tasks requiring Inventory. We’re working on a extending this MySql implementation over the coming months, which will provide even better performance in the future. The schedule for this new enhanced Inventory will be announced as part of the Roadmap discussed above.
Merritt is a production level service that provides the UC community with an easy to use tool to manage, archive, and share their content. Content can be deposited and managed via a user-interface or an API.
See also Merritt webinars: http://www.cdlib.org/services/uc3/uc3webinars.html.
Service Monitoring and Availability
Check CDL’s system status page at http://www.cdlib.org/contact/system.html.