 Good morning and welcome to this week's edition of Encompass Live. I am your host, Krista Burns, here at the Nebraska Library Commission. Encompass Live is the Commission's weekly online event. Yes, we are a webinar. You can call us that. We won't be too offended by it. Embrace the webinar. Yes, I was. The webinar that we do every Wednesday morning at normally. This week, of course, because yesterday was the New Year's Day holiday. We as a state agency were closed, as I'm sure most many places were, most of you probably. So we're doing it this week on a special day on Thursday. We did the same thing last week. Same thing, Christmas is Wednesday, so we did it on Thursday. Next week, we're back to Wednesdays. Don't get used to this. Normally, we do it every Wednesday morning. It's always at 10 a.m. Central time, as it still is today. Runs for about an hour long, depending on chat and questions and whatnot. And we do a mixture of things here, presentations, many training sessions, book reviews. Basically, as it's library related, we want to have it on the show to share with everyone. And the sessions are recorded. So if you're unable to join us on Wednesdays or Thursdays, as the case may be, you can always go to our website and see the recordings of all of our shows. Going back to the very beginning, which was in January 2009. Oh, actually. Yeah, it's been a long time. So we do bring in guest speakers on the show. And sometimes we have Library and RASP, the Library Commission staff. And that's what we have this morning. Next to me is Emily Nimsacato, who is the Catalogian Librarian here at the Nebraska Library Commission. And she's going to join us or tell us about the frame, which I know is zero about. I had never heard about it until she did. I'm not a cataloger. I don't do that. I've not even heard about it until she said, I want to come on the show and do a session about this. But then I see it something coming up. I know about Mark. That's Mark, ACR 2. I got that down. So I'll just hand it over to you, Emily. You can take it away with your presentation. Great. Thanks, Krista. And thanks to all of you for joining us on the day after a holiday here. Yeah, well made it. Where it feels like Wednesday. I don't know. I'm going to be all confused the rest of the week. But yeah, thank you for joining me. We got, yeah, like Krista said, probably a lot of non-catalogers and never even heard a big frame. And I know it's really new on the radar for a lot of people even if you are a cataloger. So I thought it would be good to get some information out there. I don't consider myself an expert on it either because it's so brand new. And I mean, obviously it's not even implemented yet. We're also cataloging with Mark. So all of you out there, I definitely welcome questions if they go along and comments. If you have anything to offer that, you know, I didn't cover or you have something to say, well, I think, you know, this can add in. Please, please jump in with comments too. Anything to contribute? What's going on there? There we go. Awesome. Okay, so let's start with the very basics. Like I said, this is going to be a very basic overview of BibFrame and what it means for the cataloging world and the library world. So what is BibFrame? Well, it is not exactly an acronym, more of an abbreviation for the bibliographic framework. That's where BibFrame comes from. And probably the most shorthand way to think of it is that it is going to be a replacement for Mark machine readable cataloging as an exchange format for bibliographic data in library catalogs and beyond, I guess. Part of it is I think that it's intended to be a computer way of formatting our records or our data so that they can be used by people who are not librarians. Mark is very, very specific to libraries. And so we want to kind of make our information work with other information out there on the web. Here is sort of a more official definition, I guess. It comes from the Library of Congress itself. I did not mention before, but this is an initiative from the Library of Congress. And they began by calling it the bibliographic framework initiative, so that's where the whole BibFrame name comes from. And it is designed to, as they say, better accommodate future needs of the library community. Mark has kind of stuck in the past and they want to move forward into web-based linked data standards. And I've highlighted the important things there. We're moving away from Mark and moving towards linked data standards, and I will talk a little bit more later about what the heck linked data means. So, you know, I've said this is kind of intended to be a replacement for Mark. I mean, that's one way of thinking, but they also kind of think of it as a whole data model, you know, vocabulary for dealing with bibliographic data. But people are all kind of hyped up about it being a replacement for Mark, you know. And I have to say that, you know, I didn't necessarily expect within my career to see that Mark would finally go by the wayside, but we've changed our thinking in a lot of ways. For one thing, Mark is meant for printing catalog cards. It was originally designed not as an online catalog, including, instead of, yes, it was designed in the 1960s for printing catalog cards at the Library of Congress. You know, that was probably cataloging back in the day. You would order cards from the Library of Congress. So even though our online catalog, the computerized catalogs function very differently from a card catalog, our system is still set up for card catalogs in a lot of ways. So that's clearly behind the times. As I mentioned before, it's only used by libraries, which is not necessarily a bad thing, but it really does kind of limit some of the things that can be done with our bibliographic data and some of the ways in which we can import data from other sources into our catalogs. Librarians were kind of ahead of the time when Mark came out. This, you know, cool programming was, you know, a really nice, efficient way to print catalog cards. But then, since then, computer science has kind of moved on, and they have developed easier-to-use standards and, more importantly, just standards that everybody on the web uses, not just librarians. Another thing that could be seen as a flaw of Mark is that it's not very specific. The Mark fields and subfields, you know, there's a lot of them, and it seems like, you know, they might, you know, break down every possible piece of information you could want to include in a catalog record. But really, you'll find out that a lot of things are used for multiple types of information. You know, the computer has no way of understanding exactly what is in a particular Mark field or a particular Mark subfield. For example, the 245 field, the subfield B, the other title information. As you'll see in this example in the 245 field, it is a subtitle. However, it can also be used for a parallel title, the translation of a title into a different language, as in this example, and the way we know the difference looking at it as humans is by the punctuation that precedes the subfield B, so the distinguishing information is not even contained within that subfield, so computers have a really, really hard time dealing with that. If you were, for example, wanting to look for only parallel titles, it would have a hard time pulling that out. And then it gets even more complicated because certain subfields can't be repeated, so when you have both a subtitle and a parallel title, it all gets lumped together into one subfield B, so it makes sense when you look at it as a user, but a computer, not so much. I chose that example because it was brought to my attention by a really good article in the Code for Lib Journal, which is freely available online, and I've got the URL there, and I remember Christa mentioned this, but all the links will be available to you when we send out the email about the recording, so you don't have to scramble to write things down here. But I recommend this one. Some of the Code for Lib stuff is way over my head, really technical computer stuff, but this one I think is a really, really good article as far as explaining some of the things that computer scientists kind of freak out when they see a mark and they go, wait, I don't understand this. So it's different than what a lot of modern computer programming languages do, and so he, Jason Tomala who wrote this article, he goes through pretty specific examples of he was trying to pull out specific pieces of information from records for, I think, musical scores he was looking at and things like that, like the fact that Field B in the 245 field was used for a lot of different things, really kind of messed up what he was trying to do, so I found it to be a really interesting read and it kind of highlights maybe the need for BibFrame and thinking beyond Mark. So that kind of gets at what the next point about why Mark is kind of not suiting our needs anymore is our thinking has kind of switched that we need data instead of records, and that's, you know, I'll get into it more when we talk about linked data and the fact that BibFrame is a linked data model, but general way of thinking about things in the computer science world now and the web programming world is to think about really small, discrete pieces of information rather than a whole catalog record that just represents one book in a library collection. You know, we want to break down pieces so we can bring out the fact that each author is an individual piece of data and so you can find other things by that author and information about that author, you know, link two sources outside the library perhaps, other things about the subject heading, so everything is just kind of creating this whole web of data so to speak, and Mark doesn't really lend a thought to that pretty well. If you look at one Mark field, you're not really going to understand a whole lot or be able to find things about that field without seeing the record as a whole. Alright, so that's the basic of what BibFrame is and why it has come to be, why we're moving away from Mark. And now I just want to cover a brief timeline I don't know what's kind of funny to call it a history of BibFrame because it hasn't really been around that long, it's more current events than history I guess but I will cover the timeline here. May of 2011 was when this bibliographic framework initiative was announced by the Library of Congress. That was pretty much toward the end of the national test that was going on for the RDA resource description access new cataloging code and one of the things that came out of that test was that they really felt that we needed to be working on a replacement for Mark in order for RDA to be really effective. And so the Library of Congress announced the bibliographic framework initiative as a way of saying, hey, we are going to work on Mark, or getting rid of Mark, we're going to take this seriously. And then in October 2011 more details were made available and when they made that announcement in May, they didn't really say what was going to replace Mark. In October of that year was when they published the bibliographic framework plan and officially announced that a linked data model was going to be used. Then about a year later, a little bit over a year later, they published what they called the BibFrame Primer or the BibFrame graph model, which really got into some of the specifics of BibFrame, which we're going to cover here later. And I will also give you the link to that. It's available online as a PDF and I'll cover that in resources later as well. Just a couple more developments that happened this past year in 2013 on the website, which I will be covering in pretty great detail called BibFrame.org was launched at the ALA Midwinter meeting as sort of the official place to go for information about BibFrame. So definitely keep that in mind as a pretty good all-around resource. And in August of 2013, so fairly recently, they updated what they call discussion papers on that website. It's on BibFrame.org. These were produced by what they call the early experimenters. A number of organizations experimenting with BibFrame and we're going to talk about those later too. And they kind of flesh out what a lot of the concepts of BibFrame are talking about. So those are good resources to read as well. And they were fairly recently added. So they're pretty up to date. Do we have any questions yet at this point? Corey? No. Jump in the link data? Alright, cool. If you have any questions throughout, just go ahead and type them in. I'm monitoring everything here in the laptop and I can throw them to Emily to handle. I certainly don't mind interruptions. So yes, please go ahead and type them in as they occur to you in case you might forget by the end of the presentation. But I do hope to have some extra time at the end and we can run over a little bit if we need to. Okay, so what the heck is link data anyway? That's kind of a good and basic foundation concept to have if you're going to be thinking about BibFrame. And it sort of helps to understand the difference between Mark and between the BibFrame model. Here is what I generally use as my official definition of link data. And by official I mean I didn't just make it up, I got it from somewhere else. Wikipedia, you can go source as any. And hence our link data is a method of publishing data on the web. It builds upon technologies that we're pretty much used to such as hypertext transfer protocol, the language for the web and URIs. But rather than using these to create content that humans can read, it sort of extends them and so it makes the information kind of understandable by computers. The meaning of the information is encoded in a way that computers can read it and kind of get what the relationship between two different pieces of information are or recognize, hey this piece of data and this piece of data are both talking about the same people and we can link them together to kind of illustrate that a little bit. Right now this is sort of what the web looks like. We have all these resources out there just web pages and web pages and more web pages and they link to each other. Hyperlinks can link web pages together but the links don't really tell us a whole lot about why these two things are related. People can pretty much link web pages together for any old reason and computers definitely don't know the reason behind these links. Here's the difference with linked data. Two things, number one, we're linking kind of more discrete pieces of data here rather than just to the monolithic web page. Also the links have more specific relationships. So those little tiny pieces of data I have there on each individual web page, you know they could be the same author or the same topic and these information from different sources are brought together through the linked data encoding. So basically speaking of encoding, here is the difference between standard HTML hypertext markup language which web pages are written in and linked data encoding. Here's HTML and the tags, basically they don't tell the computer anything about how to understand the information. They basically tell the computer how to display the information. There's an H1 tag for a heading and a P tag for a paragraph and all it tells the computer is that, hey this heading should be a little bit bigger and it should be in bold. It doesn't tell you anything about what is included in that piece of information. Here is an example of RDF resource description framework encoding an XML which is extensible markup language which is kind of similar to HTML in that it has tags but the tags instead of telling the computer how to display the information they tell the computer more about what that information is. That top tag, the RDF description that is basically an identifier for this resource we're talking about which in this case happens to be a CD and then all those other lines they describe that CD and as you can see right there in the tags you know that the computer is capable of knowing that one line is the artist, Bob Dylan, that one line is the country where the CD was produced, the United States and so on and so forth and so this is all encoded right in the programming, the encoding standard rather than having to rely on human readers to understand the information. And the thing about linked data is that relationships are key. You really want to be able to lay out how different pieces of information are related to each other and that's where the magic happens so to speak with linked data both in terms of linking as far as we're concerned library resources to other resources on the web or even on a smaller scale people can do it as sort of a discovery layer for your catalog. If you want to link resources from your catalog and your digitized archival items and your journals you can bring them together by specifying relationships between those items. Right now we're used to connecting pieces of information based on our context. When we look at a catalog record we can see title, Christmas Carol and author, Charles Dickens. We know as human readers that that means that Charles Dickens wrote this book but the computer doesn't know that and we just saw one of those pieces on their own. We wouldn't necessarily know that the record says anything about the other piece of information. With linked data these relationships are more explicit RDF is based on what's called triples. They're also called statements they're triples because they have three parts subject, predicate and object like sentences. In this case the subject and the object are entities that are related somehow and then the predicate is the relationship. In this case Christmas Carol is the subject, has author is the predicate the relationship and then Charles Dickens is the object. What this leads to is what's called a data graph we have the very simple triple there on the previous slide but then you can see it expands into this whole web of data. You can talk about a particular person and that they were the author of this one thing but then they also can tell you what field they've performed in other things that they did I got this slide from an example at the University of Nevada Las Vegas. They did a presentation about their digital collections and they bring together items from a few different digital collections they have based on kind of a link data model. And when we're talking about relationships you know the really cool part about link data is you know not just to do it from one source of data basically you know the example I told you before with the Bob Dylan CD all that information came from the same place but the really cool thing about link data is that you can bring in terms and relationships from other places. So for example again I know this is pretty technical to look at and I promise I'm not going to make you look at too much more code during the rest of this presentation but up there at the top on let's see the third line where you'll see the abbreviation DC and there's a URL after it that indicates that we're bringing in Dublin core elements which is a metadata scheme and so you know the cool part of link data is that you don't have to reinvent the wheel all the time you can you know bring in terms that people have created somewhere else relationships that people have specified somewhere else and you know sort of refurbish that for your uses. Okay so that was an overview of link data which is kind of just important to know because Bidframe is a link data model. Now we're going to get into some of the technicalities of Bidframe itself and here's where we're going to kind of explore the Bidframe.org website that I linked to earlier and all this stuff is available there so I highly recommend this as a jumping off place if you want to learn more about this. On the Bidframe.org website you'll see the basic model for Bidframe and it has what is called core classes and these are basically aspects of information in our bibliographic records in the bibliographic data we're working with. There are four of them work instance authority and annotation and I realize this probably doesn't mean much at those words by themselves but they have very specific definitions within Bidframe so here's a little diagram that they have available on the website that will help explain things. Work and instance are basically those classes refer to the stuff in our catalogs. Work is the abstract way of thinking about it and one of the concept as it existed in the creator's head for example we were talking about Tail of Two Cities earlier when Charles took in the thought of it in his head that's the abstract way and it doesn't matter if it's in French or if it was the original English publication of it it's still the same work and then the instance is the particular physical publication of it so translation as published by a French publisher would be different than the original English published by a different publisher and we'll talk about this a little bit more later when we talk about how it relates to RDA but some of you who are familiar with the Ferber model the functional requirements for bibliographic records which is the basis for RDA work is a familiar term for you guys Ferber has four classes of kind of what they call the group one entity's work expression, manifestation and item and they progress from this high level abstract concept to an actual physical item sitting on your shelf and I'll have a diagram that outlines this later but for now I guess I would say that work and manifestation are kind of combined into the the frame work sorry work and expression and then the big frame instance probably most comparable to a Ferber manifestation and then the attributes that we would think of as being part of a Ferber item kind of come into play with the annotations that describe an instance and again hopefully I'll make more sense in a few minutes a work as defined by the big frame website is a resource reflecting the conceptual essence of a cataloging resource so like I said that is the abstract existence in someone's mind an instance is the resource reflecting an individual material embodiment of the work so something that you can actually look at like I said this relates to kind of the Ferber manifestation which is a particular version like a publication you know the Penguin Books edition of something would be different than the Random House edition although I think Penguin and Random House have the same thing now I don't know those publishers keep merging exactly yeah I don't know but well an instance I think in the big frame sense is talking about all the copies of a particular you know it's not just one item that you hold in your hand so it's concrete but not exact to one item and then authority which is kind of getting away from what we think of as the Ferber model maybe is a resource reflecting key authority concepts that have defined relationships reflected in the work instance again I know this all sounds like jargon when you quote it directly from the website but authority if you're familiar with cataloging you know that we have authority records in our catalogs now and so that the authority concept in our class I should say of entities in big frame still represents that basic thing you know authorities are you know the people who write the books we want to have authorized headings for those to use our older terminology we want to have a consistent way of doing subject headings I think I'm actually going to jump out to the website here really quick there we go the frame.org this is where I'm going to start showing you where some of these resources appear on this website under vocabulary is where you'll see the things that I'm talking about now there's that little diagram that we looked at before and if you click on all these you can find out more information about work instance authority and annotation right now I wanted to show you authority and authority is the one class that has more specific types there's agents which is like a person organization somebody who created a resource a place a control term for a geographic area a temporal concept which is basically a chronological period and then a topic so those are like subject headings or topical subject headings I should say I'm going to get back to where I was and then the last core class on the big frame model is annotation and the technical definition is a resource that asserts additional information about other big frame resource basically this can be thought of as I would say attributes of a work or an instance let me actually go back to that diagram there for example for an instance the publisher is an annotation or the published app those are annotations that can describe the instance where I guess the authorities they more describe the work you know the abstract model always has the same creator or the same subject based on you know doesn't matter which publication of it it is so authorities kind of describe the work and annotations describe the instance basically so that was the five minute I don't know how long basic introduction to big frame obviously there is much much more to uncover at that bigframe.org website we're going to jump back there in a little bit and go over some of the resources they have available but I want to talk for a little bit about how big frame is related to RDA the resource description access cataloging code that officially was implemented by the Library of Congress in March of last year now 2013 I'm not used to it being 2014 yet I've been saying it's whatever this year but no it's last year now obviously as I said these are kind of tied together because it was kind of one of the conditions for the implementation of RDA was that we do some kind of substantial work towards replacing Mark because in a lot of ways a lot of the things that are contained in the RDA rules really can't be fully realized in Mark Mark doesn't allow for the kind of relationships you know they said with linked data relationships are key and Mark really doesn't allow for linking to various things the way we'd like to and the way that RDA makes possible so bigframe and Mark are kind of linked together that way here's a quote from the Library of Congress Bidframe website that says RDA is an important source of elements in the vocabulary for Bidframe even though it generally aims to be independent of any particular set of cataloging rules so that's interesting to me I mean Bidframe was kind of put out there as a major stipulation that in order to implement RDA we need to have something new but it kind of aims to go beyond RDA and like I said one of the aims is to sort of say our library data can play nice with other data out there so obviously you don't want to say that in order to use Bidframe encoding you have to be using RDA so as I pointed out before there are some differences between RDA we're used to thinking those of us who have spent time wrapping our heads around RDA and Furber are used to work expression manifestation and item and now wait we have to do works and instances so there are some differences in a way I would say that it kind of let's see one of the RDA models it's less specific I suppose and like I said before I think work and expression are wrapped into the Bidframe work and manifestation and item are kind of represented by the Bidframe instance so I think the point is to kind of dumb it down isn't quite the right word but simplify I suppose so that we can use our data with other data from that are not from libraries you know for those of you who are kind of familiar with various the point is that people can kind of set up community profiles to be more specific on their own terms but still be able to translate and play well with others for those of you who are familiar with metadata standards Dublin Core if you're familiar with that was kind of designed to be a very bare bones basic you might have richer data in your mark records or whatever if you do a crosswalk to Dublin Core then it can be simplified and other people can use it and they might transform it into I don't know mods or something else but Dublin Core is kind of the universal language but it's a simplified language that can then be transformed to other things and I kind of think that's the deal with Bidframe it's trying to simplify library data so that it can mesh with other data out there so it's not as specific as RDA but it's not exactly the same thing and the credit for this image goes to a publication that was published by NISO called Information Standards Quarterly and that's freely available on a PDF online and I've got that linked in the resources at the end too I kind of feel like the whole Bidframe and RDA thing is a case of which came first the chicken or the egg or which needs to come first I guess is the question you know some people RDA has been widely debated on cataloging lists serves as to whether it was a good idea or not and worth the expense and everything and one thing that a lot of people have brought up is it worth changing the rules when we don't have a new encoding standard yet as I said RDA is not really realized in Mark and so I guess we're kind of doing the chicken and the egg at the same time here now RDA is obviously implemented and rolling and everything so maybe we decided here we're going to do that first but they're very very interlinked I would say and in a way I think Bidframe is going to be what really makes RDA work there's another pretty interesting article that came out recently very recently in the past month or so I would say at the online library journal called in the library with the lead pipe and there's the link there that again this is freely available online or Jason W. Dean talks about Bidframe and says he refers to RDA by saying that the changing rules for metadata creation represented by RDA will also help library metadata to be more useful this is after he's already talked about how Bidframe will help but in his opinion he says to perhaps to a lesser extent than Bidframe so a lot of people think that Bidframe is an even more important revolution in cataloging and library data than RDA was and RDA definitely made a big wave even bigger things may be coming as we move away from Mark some of you know if you think that this is all pretty abstract and you know conceptual data models and all that you would be right it's definitely very abstract right now it's in the beginning stages I think it will still be a while before you know we are fully working with Bidframe but I did want to kind of give you some ways to kind of see this more practically and there are some resources at Bidframe.org that can help you do that they have what they call use cases demonstrations and tools and I'll jump back out to their website to talk about some of these and I have the URLs for all of these various tools here but you can also find them from the main Bidframe.org homepage so under documentation you'll see the use cases and use cases are kind of hypothetical situations for how people might interact with a Bidframe catalog so to speak or what a shared cooperative cataloging environment will look like when everybody is using Bidframe and so I think this is kind of cool a lot of it is still showing you kind of the really technical code behind it so I found it a little bit overwhelming but I like the idea of kind of just showing these examples of how you might use it and how it might be different conceptually from what we're used to doing and you'll see that each one has kind of this little case study hypothetical thing for example they tell you about cataloging a new instance so a new book that's not already cataloged so it has this whole scenario where this middle school library is cataloging things for its summer reading list and so they've acquired some ebooks and so they already have the physical copies of a new record so to speak we're kind of getting away from using the word record for the ebook and so it kind of goes through how they would search and what kind of response they might get in order to see that and how they could update the resource to add their whole information for the ebook rather than the physical book so that's one particular use case I thought that one that was kind of interesting was this mobile reading one they could see being useful to someone who is interested in reading Ray Bradbury's Fahrenheit 451 particularly on his tablet he has a tablet computer and so walking into his local library the library's network notices that he has a tablet and so they default to showing him only instances that he can read on his tablet so number one it only shows some ebooks and number two it only shows they know he doesn't have a Kindle so they're going to show him something that is perhaps an ePub format that will work on his tablet computer and again you know there's the really technical code here for what a search request might look like but I find those little scenarios at the beginning to be really useful for thinking about what we could do with BibBrain that maybe we can't currently do I guess it has both of those you know this one for example I would say is something that we can't currently do but things like cataloging a new instance or how you would do subject analysis or is you know kind of examples of okay there's stuff we're already familiar with and how would that work with BibBrain and it is any different from how we do it currently so I would highly recommend glancing over these use cases you can see there's quite a few there's 15 of them so it really helped me to get a more concrete idea of okay what's the difference so what basically you know we're reading about BibBrain and all this stuff and we're going okay so what what is it going to do then another resource is the demonstrations and that's up here at the top under demos and this is basically showing examples of how a catalog the front end of the public facing version of a catalog might look with BibBrain records and so they have a few different collections these records come from different places a lot of national libraries some bigger university libraries I'm going to look at the OCLC collection really quick and you'll see you can download these if you have the capability to kind of manipulate the data and you want to pay around yourself but you can also look at these examples here as these are kind of really rough bare bones what a catalog might look like that was encoded with BibBrain and some things don't look that different but one thing I wanted to point out was this example of a none such Christmas it has the main title for the actual this is a sound recording but then it also has the works that are contained so it has a separate link for each selection and these links don't actually go anywhere right now which is one thing that I find frustrating about these demonstrations like it doesn't fully perform the way you would actually see it in a catalog but not totally yeah but I imagine that what would happen is that if you clicked on each of these links for the individual songs on this sound recording you would get to a page for that it's a different work that's contained and then you can also see other CDs that might have that song on it when it comes to classical music a lot of times works appear you know it's not like a popular music album where it basically exists in one form you know this particular concerto could appear on a CD that has all of the composers work that can appear on a CD that has you know it works for French horn or a particular type of instrument so I can see that being a really useful aspect of the frame if it allows for things like that in kind of a more granular detailed way of navigating our catalog so the demonstrations are something to keep in mind on the fibframe.org website and then the last thing they have is what's called tools and this allows you to kind of play around with the data they have the comparison service which is where you enter the bibliographic identifier of a Library of Congress mark record this is not the Library of Congress control number this is the individual what appears as the 001 field in the Library of Congress record the best place to get that would be to go to the Library of Congress catalog website actually I will jump out there really quick and if you do a search you know if you just had anything in mind if you don't care what you're looking for they say you know you would type in a number between 1 and 15 million you should get something but if you had something in mind that you're looking for you can go to the Library of Congress catalog do their search look at the mark tags and copy what's in the 001 field so I will just do that this is the comparison service again and you put your fib ID number in there and search and this kind of the intermediate stuff between mark and fib frame I believe is mark XML where it's still the mark record encoded in XML you can see that basically you still have the tag numbers, the subfield codes and then when you click on this fib frame RDF slash XML tab you get different XML instead of having the tag numbers it has the fib frame topic, fib frame authority things like that one thing I wanted to show is that again looking back on stuff maybe it's kind of hard to see all the differences rather than looking at a front-facing public catalog but fib frame being sort of workable with RDA and everything the intent is to be much more specific about encoding the information so you'll notice that because the record has a copyright date instead of a publication date whatever transfer service they're using here has been programmed to recognize that and so the fib frame element is copyright date let's see I have another example that I was going to show you that has a publication date instead this is for the book called cataloging correctly for kids obviously I just grabbed books that were in my office they're all about cataloging and in this case let's see let me scroll down to the publication information because it didn't have a C in front of it they recognized that that was a publication date and in fib frame it's called a provider date apparently so it is they're both more specific rather than just having a 260 field sub-build C which could be either a copyright date or a publication date it's a more specific form of encoding so if you feel like looking at the XML too much the transformation service is kind of a useful tool on the fib frame website the other one or that that's alright that was the comparison service the other one is a transformation service and if you feel like submitting your own mark writers if you want to get really technical with this and mess around with it you have to convert it to mark XML first and there is a tool to do that on the library of congress website so I don't remember if I put that in my resources but if not I'll get the link for that to Kristen she'll include that on the show recording page so if you convert your you know export a batch of records from your catalog convert to mark XML and then you can submit that URL and have it converted to fib frame stuff so if you have the capability to play around with it and you want to see what it looks like you can go ahead and do that too so going along with practical applications there are actually libraries experimenting with fib frame I mean like I said a lot of it's theoretical right now but I mentioned before that there is the early experimenters project going on a lot of national libraries obviously they're the ones that probably have the most resources to do this but OCLC is also involved a couple of university libraries they're playing around with it I don't think any of them have necessarily products that can be seen but they're working with it they're on it so another project that I wanted to mention Colorado College and University of Denver completely separately from the early experimenters project which is kind of an initiative spearheaded by the Library of Congress who's actually developing fib frame but Colorado College and the University of Denver decided that they want to go ahead and kind of try to work things out on their own they're part of a consortium and they wanted to kind of see how fib frame encoding works with their consortium for as far as sharing records go and things like that so again Code for Lib Journal and this one is more technical than the other one that I linked to it kind of makes my head hurt a little bit but from what I understand it's really interesting quote from this article says we are currently in the early stages this is written by the Colorado College folks they say we are currently in the early stages of prototyping a peer to peer fib frame data store with the University of Denver's Penrose Library and they say once they reach what they call a critical mass of information in this they're going to replace their current mark ILS with this fib frame stuff so even though they're still experimenting with their planning on yeah right now there's nothing that I can point to and say here go look at this but there's a run to keep an eye on if you do want to see kind of an early adopter I don't know what they consider to be a critical mass I don't know if they're going to wait for any kind of go ahead from the Library of Congress before they unveil it but they feel they've got a good enough handle on the frame to go ahead and start playing around with it so that's something to keep an eye on so with that said what is next what are we looking at here people I know are often asking is there a timeline for this when are we going to see this and we have to know yeah exactly yeah send it with RDA you know people are wanting to know okay when is this going to happen and the short answer to the question is there a timeline is no I think they're really you know avoiding tying themselves down to anything like I said it's highly theoretical right now on the bib frame website you know I looked and looked to see are they even trying to make any predictions and this is the quote I found the mark standard is possible for the creation of millions of bibliographic records and they recognize the need to continue supporting Mark and most likely for years to come so there's not going to be any you know yeah you're not going to have to wait for a long time probably so and it seems like libraries are going to be kind of determining their own timetable for making the change right now I think we're kind of you know it's obviously going to depend on what software is out there when our library vendors going to start dealing with this so I think we're going to kind of be in a holding pattern for a while here still something that people are probably wondering about is how is this going to fight catalogers on a daily basis of is this going to totally take catalogers out of business I don't think so I certainly hope not but I think that our jobs will change that is for sure I mentioned this issue of information standards quarterly before I highly recommended it's in my links there's four or five different articles that are all really relevant to big frame and metadata happenings the this is from an interview with a person from the French National Library and they've been doing a lot honestly I think other countries have been doing a lot more with big frame and you know link data than America has to be honest but his quote was I believe we will need certainly need to change most of our cataloging habits standards and tools but that losing the quality and granularity of the data itself should not be a requirement I mean we may have kind of gotten stuck in the past as far as the actual encoding standard goes with Mark but really librarians are on the ball when it comes to recognizing things like controlled vocabulary and high quality data that's accurate and you know I think we have a lot to offer the whole web community you know they're kind of figuring things out when I'm getting into link data they're going oh hey we need control vocabulary we need to refer to the same thing way all the time and librarians are like oh we knew that so our skillset I think is still very, very, very relevant you know yes our tools will change and our jobs may become more about evaluating metadata rather than creating it bringing in things and saying hey this matches what we already have or saying oh I think authority work will still be very important the idea with link data is that you know each person or each subject heading will be represented by a URI a concept out there on the web but you know we also have to recognize when there isn't a URI for something and we'll probably be doing things like creating URIs instead of creating authority records but it's still the same basic concept and I think we have a lot to offer in fact I think one of those use cases on the the big frame website was creating a URI for an authority so yeah we're still going to be using our same skills you know I'm going back to that RDF example about the Bob Dylan CD somebody had to decide that artist is the term that's going to be used, that country is the term that's going to be used, these are controlled vocabularies these are what we do with subject headings librarians are still relevant catalogers are still going to be relevant that's for sure so that were my basic take on the I'm like I said the very basics of it for those of you who have attended my presentations before you know that I really like to throw a lot of resources at you you can only cover you can only cover so much in an hour and I like to do the work for you as far as finding the things that I find really informative out there there's a lot out there especially with stuff on the internet these days most of my resources are web resources that are freely available as I said I think I mentioned before the Library of Congress has what they call their informational site about BibFrame that is separate from the BibFrame.org site the bibliographic framework as a web of data is a PDF report that is also referred to as the BibFrame Primer so that is a very, very good place to start out with then I've definitely already been talking about the BibFrame.org website a lot if you really want to be immersed in BibFrame there is a listserv you can browse the archives at that website that I've included from that page it will also tell you how to subscribe to that list if you want to I subscribe to it and to be honest a lot of it is over my head and I just kind of skip it and go okay I'll maybe read that thread later when I have time so you may want to subscribe you may want to just look at the archives and see if there's topics that are relevant to you but the listserv is a good place to kind of figure out what's going on I know there are announcements that there's developments or new discussion papers, things like that so that's a good reason to be on the list I've already mentioned this one several times but that most recent issue of information standards quarterly is available as a PDF online and there are four or five different articles in there that are really useful that interview with the guy from the French National Library I thought was really cool and then I mentioned before that in the library with the lead pipe article I already threw that URL at you that's a good overview of the frame and how it relates to kind of the cataloging tradition an article in library journal that came out fairly recently was called link data in the creases and it's really that was kind of a different take on link data you know the author sort of expressed her opinion that I think why people are having a hard time getting excited about link data is that for just seeing it in kind of of it as an alternative to mark you know really doesn't highlight it's really cool aspects because you're just dealing with the resources that your library has you're not seeing the whole linking capability of it but like archival collections and special collection stuff where you can bring together resources from different institutions things like that she really highlights it got me kind of fired up about link data and where we're going with that OCLC of course it has their fingers in this they really want to be on the pulse of what's happening with bibliographic data so they have a working paper on what they've been doing with big frame and you know link data and the world cat data and like I said I mostly link to things that are freely available on the web but I did want to include a print resource that is available through cataloging and classification quarterly because it is written by one of our very own Nebraskans Angela Craig from UNO she recently published an article about the road to big frame and so that link that I've given you will be the landing page for the journal but if you don't actually subscribe to it you won't be able to read it from there but it's cataloging classification quarterly so keep an eye out for that it's led to a really good job of outlining the kind of developments that led to big frame the thinking behind why it's important that article is where I found out about the University of Denver and the Colorado College project so Angela is clearly on top of the latest developments so that's basically it does anybody have any questions I didn't see anything come in during the show but if you have any questions use your questions section of your go to webinar interface and you'll end up here no if you have any questions, comments any of your own thoughts are you avoiding this completely you don't have to know yet I know it was a loss to take in maybe everybody's just too stunned to ask questions I was talking in my element at the whole time but it's a lot to cover it's a lot of creation out there well it's something new once again coming out that we've got to pay attention to because it's going to it's going to be there obviously at the same time as Mark was still being used and everything so that's good yeah there's a transition there's no mandate that you have to do this now like I said a lot will depend on the vendors it's the same thing with RDA right we have to wait for them to really add all this to their systems they want to use it all they want but if it's not available and the systems and vendors that we're working with they're exploring it too yeah I assume so I was the OCLCs they're probably going to incorporate it into the whole world share whatever their thing is called now but I think the Colorado thing is interesting because maybe libraries are going to move away you know kind of more homegrown stuff I don't know there are a lot of libraries doing that with various things like ebooks and collections like that saying we do have the skill and the technology to do some of this ourselves some of the larger ones obviously tomorrow libraries are going to be more dependent but if they can experiment with it and figure it out for us that's good all for that let's see we do just have a comment yeah still pretty new for me I admit but thanks so much for breaking down the key elements so that I can share with my colleagues and start figuring this out here in and she is in Colorado awesome I remember when we first started sessions on RDA it was like this same thing yeah you don't need to know about yet here's the basics things will change probably but just have this on your horizon alright doesn't look like any urgent questions have come in so that's fine the session is being recorded the slides will be posted when the recording is up that you'll all be notified when that is and all the links I caught most of them while we were doing the show but I'll go back and make sure I grab all of them all the links will be made available to you as well when I send you out the recording information so you'll have that too so other than that since we don't have any urgent questions it looks like coming in I think we will wrap it up for today did you want to go to the Encompass live yeah okay so thank you Emily for getting us up to speed as far as we can be and thank you everyone for attending I hope it was useful to you I know I have like I said I'm not a cataloger so a lot of it I get it I do I have to know just what's going on to be able to work in the library also thank yous and they actually enjoyed this presentation so that we'll wrap it up for this morning the show has been recorded you'll get that information later this afternoon we get up so that wrap it up for today's show I hope you join us next week when we have a Nebraska-centric episode internships cultivating Nebraska's future librarians where we're going to hear from here at the Nebraska library commission we have our 21st century librarian internship grant program that we've been doing for quite a few years I'm not even sure how long it's been and every year we give grants to librarians to go to conferences get their degrees and whatnot help them do things and we're going to hear from some of the people who got the grants this past year 2013 and how to apply for the next year's grants so if you're a Nebraska librarian definitely check into this to see if you can see who has been using how you can use it and even if you're not a Nebraska librarian see what we're doing here and maybe get some thoughts for your library so I hope you sign up for that next week also Encompass Live is on Facebook so if you are a big Facebook user you can pop over there and like us on Facebook and you'll get notifications mainly it's just announcements of what next show is coming up when a recording is available this morning I did the recording for last week's show that posted and then we do a reminder message for the current today's show so they'll just keep you up to date that way so if you are big on Facebook and you want to be notified through there go ahead and like the Encompass Live page there other than that that will wrap it up this morning we're a little left 11 pretty much perfect time we started a little after 10 so thank you very much and that was our first show 2014 the first show we've been doing this for 5 years now this is the first show of the 6th year we started in January 2009 we did a nice round year to start right at the beginning so welcome to 2014 Encompass Live and we'll see you next time thanks