As libraries' collections increasingly go digital, so too does their dependence on knowledgebases to access and maintain these electronic holdings. Somewhat different from other library-based knowledge management systems (catalogs, institutional repositories, etc.), the data found in the knowledgebases of link resolvers or electronic resource management systems are not generally modeled, created, or updated by librarians. Much like working with the subscription-based resources they track, it is difficult to know what exactly libraries are allowed to "do" with their knowledgebase data. Outside of the obvious potential it brings to the evolution of the knowledgebase as librarians currently know it--a standard for publishers and providers to point to for their holdings submissions; a centralized source to add and disseminate targets provided by librarians when the vendor community cannot or will not; and a means to eliminate the redundancies of maintaining multiple knowledgebases between vendor offerings--the community-contributed knowledgebase also creates opportunities for new services. Since the knowledgebase crisis is not going away, and as the digital universe expands, especially to new and different formats, it will only get more difficult to manage. The author contends that by tapping into the power of the entire community--from the beginning of the publishing chain to the end-user--the knowledgebase becomes self-sustaining and finds new and interesting uses along the way. (Contains 10 notes.)