Yes, and I think a crucial part in case 2 that is missing is, especially 
when doing research, a user wants to find information they didn't know 
they wanted (or where to look). That means, they don't know which 
specific journal they need to look in... they don't know the specific 
database or web site... they would like to query from much more than a 
local OPAC. They just want (good) information. 

This situation of serendipitous discovery is where linked data is 
uniquely poised to offer added value, and it is possible because 
machines know the relationships we're putting into the data, not just a 
key/value pair, as in non-linked data. 


On Fri, 3 Feb 2017 19:58:37 +0000, Stephen Meyer 
<[log in to unmask]> wrote:

>I think that reducing the use cases to these two historical functions 
of the catalog might miss Karen's point in why she raises the knowledge 
card enhancement of a discovery experience. We would not have invested 
the time in the prototype if we believed our catalog could serve only 
known item and simple topical discovery.
>Here I would draw upon the *formal* definition of a user story from 
agile software development practices (As a..., I want..., So that...). 
These two cases below only cover up to the want, but not the purpose (so 
>As a student writing a term paper
>I want to find information about Gertrude Stein
>So that I can develop the understanding required to discuss her work's 
meaning and impact
>The library's job wraps up at the discovery and access, but the user's 
job is just beginning at this point of actually using and engaging with 
the material. So if we conceptualize information seeking as not the end, 
but a step en route to understanding, then yes, a knowledge/info card 
card is an attempt to enrich the end goal (understanding) not 
intermediary goal (finding).
>> On Feb 3, 2017, at 1:02 PM, Jeff Edmunds <[log in to unmask]> wrote:
>> The 2 basic use cases for libraries (that involve collections) are:
>> 1) User wants to find a specific item (howsoever item is defined).
>> 2) User wants to find a manageable amount of information about a
>> specific topic.