The Massachusetts Library Network Cooperative (MassLNC) is seeking quotes for the following development projects.
- Enhacements to Evergreen Alerts - The goal of this project is to improve the control staff have in creating/managing item alerts and to improve workflow when handling alerts.
- Work Log Improvements - Add retrieved patrons to the work log and improve name display.
- Shelf-Expired Holds Should Not Include Items Expiring Today - When selecting Clear Shelf-Expired Holds from the Circulation menu or when selecting View Shelf-Expired Holds from the Browse Holds Shelf interface, the resulting list should only include items that expired before today.
- Direct Access to Edit Items - The system should provide a more direct means for editing copy records.
Instructions for Developers
MassLNC invites developers and vendors to submit quotes for one or any number of the requested enhancements. If submitting a quote for the Evergreen alert projects or the work log improvements, please provide a separate quote for each individual project except in cases where you believe an integrated approach is required to support two or more projects.
- When submitting a quote, please include an estimated cost of service, a projected timeline and a description of the proposed development. All quotes are due by 11:59 p.m. EST Thursday, November 14.
- If you have questions about the scope or approach for any project, please send them to MassLNC Project Coordinator Kathy Lussier at email@example.com by 5 p.m. EST November 7. MassLNC will respond to these questions as they are received via e-mail and will also post the responses to the MassLNC site so that all developers can benefit from the same information.
- Any enhancements that result from this work should not negatively impact system performance. MassLNC will perform tests before and after new code is added to verify that performance is not diminished.
Every proposal for this work should include a section that addresses performance.
If the developer/vendor believes the work cannot be done without some negative impact on performance, the proposal should describe where performance issues may arise and the expected severity of the performance impact.
Conversely, if there are opportunities to improve performance in the course of this project, those opportunities should be outlined along with any additional financial costs that might arise as a result of doing the project in a way that leads to improved performance.
If the developer/vendor does not anticipate any positive or negative impacts to performance, this fact should also be clearly stated in the proposal
- If MassLNC contracts with a developer, MassLNC expects the developer to share plans and communicate with the Evergreen developer community to help ensure the code is acceptable to the community.
- Prior to coding, MassLNC expects the developer to do one of the following to communicate their plans:
- Submit a report to Launchpad (http://launchpad.net/evergreen) to share detailed technical information about the proposed development. Preferred
- Post formal specs to a place that is easily accessible to the developer community.
- Send a message to the Evergreen developer’s list (http://libmail.georgialibraries.org/mailman/listinfo/open-ils-dev) to share detailed technical information about the proposed development.
- MassLNC plans to finalize decisions by December 1, 2013.