OCLC Community Center

Description of Enhancement As a team leader, I want to be able to see all of the enhancements suggestions submitted or rated by individuals associated with my institution so that: We can give subject matter experts responsibility for submiting suggestions and ratings/reviews, but still get a complete picture of what is being requested and why. We can compare release notes against enhancements suggestions and ratings/reviews made by our institution to inform configuration decisions. Staff turnover does not impact processes and corporate knowledge. This would provide similar functionality to Zendesk where I can see: My requests Requests I'm CC'd on Organization requests Issues Enhancement Will Resolve Currently I can only see my individual suggestions and ratings. This makes it difficult to prioritse and manage enhancement suggestions across the institution. Current Workaround Our work around involves tracking enhancement suggestions in an Excel spreadsheet before submitting them to the Community Center. ... View more

Description of Enhancement When OCLC works on the implementation of an enhancement request, the product team or developer should ask the original submitter of the request for feedback on the proposed implementation. This will make sure the chosen approach actually solves the original problem that prompted the request. It would be even better to post the proposed solution as a reply to the original request, so other users can also comment. Quite often other people support a request and those people may have an opinion about the proposed implementation as well. Issues Enhancement Will Resolve Enhancement requests can be tricky to interpret. This can be because the request itself is not clearly defined, or because the product team or a developer think they know what is meant and how to program the feature. This can lead to OCLC thinking it solved a request, but the submitter being disappointed in the way it has been implemented. If OCLC were to contact the submitter and explain how developers plan to build the solution, this might be helpful. As an example, two requests that have been closed because OCLC thinks an implemented feature (Search by role in Admin) solved an issue (a report of roles). Current Workaround Create a new request, explain why it is different from the new/existing functionality (and the associated process of gathering commnity support and waiting for it to be picked up by the product team) ... View more