I started preparing a longer answer to this, and still will provide one 
eventually.

But first, to really answer the question, we need some more information 
from you. What data do you actually have of value? Just saying "we have 
FRBRized data" doesn't really tell me, "FRBRized data" can be almost 
anything, really.   Can you tell us more about what value you think 
you've added to your data as a result of your "FRBRization"?  What do 
you have that wasn't there before?  Better relationships between 
manifestations?  Something else? 

I forget, were you focusing on specific material types (music or moving 
image?) in this project, or is this just general materials, covering the 
gamut of what one would expect from a major academic library?  If you've 
done special work with music or moving image, what is the nature of the 
value added there?

Do these questions make sense?   To know how I might want to use the 
data, I need to know a bit more about what you've actually got that's 
useful, which "it's FRBRized" doesn't really tell me. 

But as far as "do you want real-time querries to a web service, or bulk 
download of the data?" -- yes, I'd want both, probably. Either one will 
be the most convenient depending on what I'm trying to do. If you _had_ 
to pick one, it would be 'bulk download', because _anything_ is possible 
with bulk download -- but for certain uses, it can take a lot more work 
on my part for bulk download, so if that's all there is there, it will 
be a higher barrier for use than if real-time web api was available.  
But if _only_ real-time querries are available, then certain things are 
just impossible (mainly indexing-time enhancement of my data).  

Jonathan

Riley, Jenn wrote:
> Hi all,
>
> At Indiana University we're working on a project that will help us see
> concretely what FRBRized [1] library data and discovery systems might look
> like. [2] One of our project goals is to share the raw FRBRized data widely
> so that others can look at it to see how it's structured, reuse it, improve
> on it, comment on the FRBRization effectiveness, etc. We're planning on
> allowing remote/Web Services/API/SRU/some machine-to-machine method like
> that access to the data. As we're starting to think about how we should set
> that up, we thought it would be useful to gather some use cases from the
> code4lib community, as it's the folks here that are experimenting with
> services like this. So if there were FRBRized data available to you (at
> least for FRBR group 1 and group 2 entities; *maybe* group 3 as well), what
> would you do with it? What kinds of questions would your service (discovery
> system, whatever) ask a service that made this data available? What kinds of
> information would you want in a response? Would you have uses that called
> for downloading of "all" data at once or would you instead be better off
> with real-time queries to a web service? It's questions like that we're
> interested in brainstorming with this group about.
>
> Basically, what type of access to the data we're generating is most
> important, since we have finite resources to expend on this right now.
>
> Thanks, all!
>
> Jenn
>
> [1] http://www.loc.gov/cds/downloads/FRBR.PDF
> [2] http://vfrbr.info
>
> ========================
> Jenn Riley
> Metadata Librarian
> Digital Library Program
> Indiana University - Bloomington
> Wells Library W501
> (812) 856-5759
> www.dlib.indiana.edu
>
> Inquiring Librarian blog: www.inquiringlibrarian.blogspot.com
>
>