Kyle Banerjee asks:
> I feel there is another issue at play, namely that librarians are sometimes too quick to let others
> dump their grunt work on them. For example, if it's important for a department to track its own
> output when they know better than anyone else who is involved and what they want to track,
> why do they expect to hand this problem to librarians who will just parse through a bunch Of
> inconsistent and incomplete data they find and cobble together on their own? It's complicated,
> way more labor intensive and less accurate than anything the department would do, and
> doomed to failure out the door.
One sad problem I have seen is that the departments (or the members of the departments) _don't_ really want to track their own output, because they are afraid that it will end up being used to evaluate their performance. The larger organization wants to track output for promotional purposes and encouraging collaboration between departments and organizations, but the departments oppose efforts to require it. That leaves organizations floundering for other solutions.
[log in to unmask]