Re: [CODE4LIB] COinS metadata format support
The COinS generator was an instance of the 1Cate/Worldcat Link Manager software, which has been retired. A replacement would be an hour or two of work in RoR or Django, very suitable for a hackathon. I’d be happy to consult if anyone wants it. I continue to be surprised at the ratio of success/adoption for COinS to the amount of work invested in it, especially compared to other things I’ve been involved with. There’s a lesson there somewhere. Eric Hellman President, Gluejar.Inc. Founder, Unglue.it https://unglue.it/ http://go-to-hellman.blogspot.com/ twitter: @gluejar On Jan 17, 2014, at 12:54 PM, Jodi Schneider wrote: > In case it helps there's more info here: > http://ocoins.info/ > (though it looks like the generator isn't up any longer, maybe due to "OCLC > New Jersey" hosting?)
Re: [CODE4LIB] COinS metadata format support
Roy, I'm not sure what tips you over into sarcasm mode (unless it's
anything I say), but 1) the answer is a few posts down, albeit not in
any detail 2) as a member-based organization that exists to serve its
members, I would think that OCLC would want to encourage the gathering
of information about members needs, rather than responding to them
negatively.
The transition to a new data model, and in particular the use of
identifiers for things, is (IMO) going to open up a lot of opportunities
for services. This will be like the transition to MARC from cards
("retrospective conversion") and the transition from AACR headings to
AACR2 headings, on steroids. It's not too early to start, and one of the
early steps is that of matching our string-based data with URIs for the
same thing. I'd be interested in engaging in some brainstorming about
how to make this happen as efficiently and cost effective as possible.
(Maybe this would be a good BOF at c4l14?)
kc
On 1/17/14, 2:10 PM, Roy Tennant wrote:
I agree that most Schema.org markup would be generated on the fly from a
database, so I'm a bit unclear on what kind of "tool" we (OCLC) or someone
else is being asked to develop. Perhaps someone could spell it out for this
dense person? Thanks,
Roy
On Fri, Jan 17, 2014 at 12:02 PM, Karen Coyle wrote:
Dave, my impression is that most schema.org code is being generated
programmatically out of database-driven web sites. The list of tools (not
many) is here:
http://schema.rdfs.org/tools.html
As OCLC is very involved in schema.org, it would make sense to encourage
them to develop something. Looking at what they do today in WorldCat, the
big advantage that they seem to have is that they can locate URIs for names
(VIAF) and subjects (LCSH).
kc
On 1/17/14, 10:49 AM, Bigwood, David wrote:
Is there an easy-to-use tool for schema.org microdata? I was fond of the
OCLC NJ COinS tool, but it has gone. Anything of that ilk?
Thanks,
Dave
-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
Michael J. Giarlo
Sent: Friday, January 17, 2014 12:34 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] COinS metadata format support
Chad,
In that case, I wonder if you might get more mileage out of
schema.orgmicrodata instead of COinS. There are undoubtedly more clients
out there that can make sense of HTML5 microdata than COinS, which is
really showing its age and is a niche technology.
-Mike
On Fri, Jan 17, 2014 at 10:25 AM, Chad Mills
wrote:
Jodi,
No. I am working with our repository resources which is an eclectic
mixture of resource types. I just want to simply embed our metadata
in our search results and record displays for other tools to use. It
seems cheap and reasonable to do I just didn't want to limit this
feature to only certain resource types.
Best,
Chad
- Original Message -
From: "Jodi Schneider"
To: CODE4LIB@LISTSERV.ND.EDU
Sent: Friday, January 17, 2014 12:54:43 PM
Subject: Re: [CODE4LIB] COinS metadata format support
Hi Chad,
Are these subscription images/video/audio that libraries have? The
original purpose of COinS, as I understand it, was to get people to
subscription copies. Depending on what you're doing (i.e. the
purpose/intended use) there might be a better standard these days.
In case it helps there's more info here:
http://ocoins.info/
(though it looks like the generator isn't up any longer, maybe due to
"OCLC New Jersey" hosting?)
Hopefully you'll get some more helpful advice from others!
-Jodi
On Fri, Jan 17, 2014 at 5:36 PM, Chad Mills
wrote:
I was able to easily find and create COinS for books and journals.
I started thinking about images, video, audio, etc. I see
references to 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value
some places. I
would
assume if I went down that road the rft.genre would have a value of
'unknown' as well. Is there some other alternative I am missing
when handling other formats?
Thanks!
--
Chad Mills
Digital Library Architect
Ph: 848.932.5924
Fax: 848.932.1386
Cell: 732.309.8538
Rutgers University Libraries
Scholarly Communication Center
Room 409D, Alexander Library
169 College Avenue, New Brunswick, NJ 08901
http://rucore.libraries.rutgers.edu/
--
Karen Coyle
kco...@kcoyle.net http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet
--
Karen Coyle
kco...@kcoyle.net http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet
Re: [CODE4LIB] COinS metadata format support
I agree that most Schema.org markup would be generated on the fly from a database, so I'm a bit unclear on what kind of "tool" we (OCLC) or someone else is being asked to develop. Perhaps someone could spell it out for this dense person? Thanks, Roy On Fri, Jan 17, 2014 at 12:02 PM, Karen Coyle wrote: > Dave, my impression is that most schema.org code is being generated > programmatically out of database-driven web sites. The list of tools (not > many) is here: > > http://schema.rdfs.org/tools.html > > As OCLC is very involved in schema.org, it would make sense to encourage > them to develop something. Looking at what they do today in WorldCat, the > big advantage that they seem to have is that they can locate URIs for names > (VIAF) and subjects (LCSH). > > kc > > On 1/17/14, 10:49 AM, Bigwood, David wrote: > >> Is there an easy-to-use tool for schema.org microdata? I was fond of the >> OCLC NJ COinS tool, but it has gone. Anything of that ilk? >> >> Thanks, >> Dave >> >> -Original Message- >> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of >> Michael J. Giarlo >> Sent: Friday, January 17, 2014 12:34 PM >> To: CODE4LIB@LISTSERV.ND.EDU >> Subject: Re: [CODE4LIB] COinS metadata format support >> >> Chad, >> >> In that case, I wonder if you might get more mileage out of >> schema.orgmicrodata instead of COinS. There are undoubtedly more clients >> out there that can make sense of HTML5 microdata than COinS, which is >> really showing its age and is a niche technology. >> >> -Mike >> >> >> >> On Fri, Jan 17, 2014 at 10:25 AM, Chad Mills >> wrote: >> >> Jodi, >>> >>> No. I am working with our repository resources which is an eclectic >>> mixture of resource types. I just want to simply embed our metadata >>> in our search results and record displays for other tools to use. It >>> seems cheap and reasonable to do I just didn't want to limit this >>> feature to only certain resource types. >>> >>> Best, >>> Chad >>> >>> >>> - Original Message - >>> From: "Jodi Schneider" >>> To: CODE4LIB@LISTSERV.ND.EDU >>> Sent: Friday, January 17, 2014 12:54:43 PM >>> Subject: Re: [CODE4LIB] COinS metadata format support >>> >>> Hi Chad, >>> >>> Are these subscription images/video/audio that libraries have? The >>> original purpose of COinS, as I understand it, was to get people to >>> subscription copies. Depending on what you're doing (i.e. the >>> purpose/intended use) there might be a better standard these days. >>> >>> In case it helps there's more info here: >>> http://ocoins.info/ >>> (though it looks like the generator isn't up any longer, maybe due to >>> "OCLC New Jersey" hosting?) >>> >>> Hopefully you'll get some more helpful advice from others! >>> >>> -Jodi >>> >>> >>> >>> >>> On Fri, Jan 17, 2014 at 5:36 PM, Chad Mills >>> wrote: >>> >>> I was able to easily find and create COinS for books and journals. >>>> I started thinking about images, video, audio, etc. I see >>>> references to 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value >>>> some places. I >>>> >>> would >>> >>>> assume if I went down that road the rft.genre would have a value of >>>> 'unknown' as well. Is there some other alternative I am missing >>>> when handling other formats? >>>> >>>> Thanks! >>>> >>>> -- >>>> Chad Mills >>>> Digital Library Architect >>>> Ph: 848.932.5924 >>>> Fax: 848.932.1386 >>>> Cell: 732.309.8538 >>>> >>>> Rutgers University Libraries >>>> Scholarly Communication Center >>>> Room 409D, Alexander Library >>>> 169 College Avenue, New Brunswick, NJ 08901 >>>> >>>> http://rucore.libraries.rutgers.edu/ >>>> >>>> > -- > Karen Coyle > kco...@kcoyle.net http://kcoyle.net > m: 1-510-435-8234 > skype: kcoylenet >
Re: [CODE4LIB] COinS metadata format support
Chad, Definitely, I recently added more metadata support to my system. To do that, I added Schema.org microdata, COinS, and Highwire Press tags for Google Scholar. I was tempted to implement the old fashioned Dublin core tags, but held back in case it would mean those fields would be double indexed. I haven't had any systems balk at receiving too much metadata in the page. Mark / UF -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Chad Mills Sent: Friday, January 17, 2014 1:46 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] COinS metadata format support Mike, I initially started with microdata; larger coverage... Someone reminded me about COinS and that has gotten me distracted now. Been weighing both back and forth in my mind. Why not both? Can I have my cake and eat it too? I like cake, Chad - Original Message - From: "Michael J. Giarlo" To: CODE4LIB@LISTSERV.ND.EDU Sent: Friday, January 17, 2014 1:33:45 PM Subject: Re: [CODE4LIB] COinS metadata format support Chad, In that case, I wonder if you might get more mileage out of schema.orgmicrodata instead of COinS. There are undoubtedly more clients out there that can make sense of HTML5 microdata than COinS, which is really showing its age and is a niche technology. -Mike On Fri, Jan 17, 2014 at 10:25 AM, Chad Mills wrote: > Jodi, > > No. I am working with our repository resources which is an eclectic > mixture of resource types. I just want to simply embed our metadata > in our search results and record displays for other tools to use. It > seems cheap and reasonable to do I just didn't want to limit this > feature to only certain resource types. > > Best, > Chad > > > - Original Message - > From: "Jodi Schneider" > To: CODE4LIB@LISTSERV.ND.EDU > Sent: Friday, January 17, 2014 12:54:43 PM > Subject: Re: [CODE4LIB] COinS metadata format support > > Hi Chad, > > Are these subscription images/video/audio that libraries have? The > original purpose of COinS, as I understand it, was to get people to > subscription copies. Depending on what you're doing (i.e. the > purpose/intended use) there might be a better standard these days. > > In case it helps there's more info here: > http://ocoins.info/ > (though it looks like the generator isn't up any longer, maybe due to > "OCLC New Jersey" hosting?) > > Hopefully you'll get some more helpful advice from others! > > -Jodi > > > > > On Fri, Jan 17, 2014 at 5:36 PM, Chad Mills > wrote: > > > I was able to easily find and create COinS for books and journals. > > I started thinking about images, video, audio, etc. I see > > references to 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value > > some places. I > would > > assume if I went down that road the rft.genre would have a value of > > 'unknown' as well. Is there some other alternative I am missing > > when handling other formats? > > > > Thanks! > > > > -- > > Chad Mills > > Digital Library Architect > > Ph: 848.932.5924 > > Fax: 848.932.1386 > > Cell: 732.309.8538 > > > > Rutgers University Libraries > > Scholarly Communication Center > > Room 409D, Alexander Library > > 169 College Avenue, New Brunswick, NJ 08901 > > > > http://rucore.libraries.rutgers.edu/ > > >
Re: [CODE4LIB] COinS metadata format support
Dave, my impression is that most schema.org code is being generated programmatically out of database-driven web sites. The list of tools (not many) is here: http://schema.rdfs.org/tools.html As OCLC is very involved in schema.org, it would make sense to encourage them to develop something. Looking at what they do today in WorldCat, the big advantage that they seem to have is that they can locate URIs for names (VIAF) and subjects (LCSH). kc On 1/17/14, 10:49 AM, Bigwood, David wrote: Is there an easy-to-use tool for schema.org microdata? I was fond of the OCLC NJ COinS tool, but it has gone. Anything of that ilk? Thanks, Dave -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Michael J. Giarlo Sent: Friday, January 17, 2014 12:34 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] COinS metadata format support Chad, In that case, I wonder if you might get more mileage out of schema.orgmicrodata instead of COinS. There are undoubtedly more clients out there that can make sense of HTML5 microdata than COinS, which is really showing its age and is a niche technology. -Mike On Fri, Jan 17, 2014 at 10:25 AM, Chad Mills wrote: Jodi, No. I am working with our repository resources which is an eclectic mixture of resource types. I just want to simply embed our metadata in our search results and record displays for other tools to use. It seems cheap and reasonable to do I just didn't want to limit this feature to only certain resource types. Best, Chad - Original Message - From: "Jodi Schneider" To: CODE4LIB@LISTSERV.ND.EDU Sent: Friday, January 17, 2014 12:54:43 PM Subject: Re: [CODE4LIB] COinS metadata format support Hi Chad, Are these subscription images/video/audio that libraries have? The original purpose of COinS, as I understand it, was to get people to subscription copies. Depending on what you're doing (i.e. the purpose/intended use) there might be a better standard these days. In case it helps there's more info here: http://ocoins.info/ (though it looks like the generator isn't up any longer, maybe due to "OCLC New Jersey" hosting?) Hopefully you'll get some more helpful advice from others! -Jodi On Fri, Jan 17, 2014 at 5:36 PM, Chad Mills wrote: I was able to easily find and create COinS for books and journals. I started thinking about images, video, audio, etc. I see references to 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value some places. I would assume if I went down that road the rft.genre would have a value of 'unknown' as well. Is there some other alternative I am missing when handling other formats? Thanks! -- Chad Mills Digital Library Architect Ph: 848.932.5924 Fax: 848.932.1386 Cell: 732.309.8538 Rutgers University Libraries Scholarly Communication Center Room 409D, Alexander Library 169 College Avenue, New Brunswick, NJ 08901 http://rucore.libraries.rutgers.edu/ -- Karen Coyle kco...@kcoyle.net http://kcoyle.net m: 1-510-435-8234 skype: kcoylenet
Re: [CODE4LIB] COinS metadata format support
Chad, You can have both, sure! I'm just wondering how many users of your repository will have a COinS-aware client, mostly. You know, the bang-for-buck thing. If you've got enough bucks and time, though, go for both? :) -Mike On Fri, Jan 17, 2014 at 10:45 AM, Chad Mills wrote: > Mike, > > I initially started with microdata; larger coverage... Someone reminded > me about COinS and that has gotten me distracted now. Been weighing both > back and forth in my mind. Why not both? Can I have my cake and eat it > too? > > I like cake, > Chad > > > - Original Message - > From: "Michael J. Giarlo" > To: CODE4LIB@LISTSERV.ND.EDU > Sent: Friday, January 17, 2014 1:33:45 PM > Subject: Re: [CODE4LIB] COinS metadata format support > > Chad, > > In that case, I wonder if you might get more mileage out of > schema.orgmicrodata instead of COinS. There are undoubtedly more > clients out there > that can make sense of HTML5 microdata than COinS, which is really showing > its age and is a niche technology. > > -Mike > > > > On Fri, Jan 17, 2014 at 10:25 AM, Chad Mills >wrote: > > > Jodi, > > > > No. I am working with our repository resources which is an eclectic > > mixture of resource types. I just want to simply embed our metadata in > our > > search results and record displays for other tools to use. It seems > cheap > > and reasonable to do I just didn't want to limit this feature to only > > certain resource types. > > > > Best, > > Chad > > > > > > - Original Message - > > From: "Jodi Schneider" > > To: CODE4LIB@LISTSERV.ND.EDU > > Sent: Friday, January 17, 2014 12:54:43 PM > > Subject: Re: [CODE4LIB] COinS metadata format support > > > > Hi Chad, > > > > Are these subscription images/video/audio that libraries have? The > original > > purpose of COinS, as I understand it, was to get people to subscription > > copies. Depending on what you're doing (i.e. the purpose/intended use) > > there might be a better standard these days. > > > > In case it helps there's more info here: > > http://ocoins.info/ > > (though it looks like the generator isn't up any longer, maybe due to > "OCLC > > New Jersey" hosting?) > > > > Hopefully you'll get some more helpful advice from others! > > > > -Jodi > > > > > > > > > > On Fri, Jan 17, 2014 at 5:36 PM, Chad Mills > > wrote: > > > > > I was able to easily find and create COinS for books and journals. I > > > started thinking about images, video, audio, etc. I see references to > > > 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value some places. I > > would > > > assume if I went down that road the rft.genre would have a value of > > > 'unknown' as well. Is there some other alternative I am missing when > > > handling other formats? > > > > > > Thanks! > > > > > > -- > > > Chad Mills > > > Digital Library Architect > > > Ph: 848.932.5924 > > > Fax: 848.932.1386 > > > Cell: 732.309.8538 > > > > > > Rutgers University Libraries > > > Scholarly Communication Center > > > Room 409D, Alexander Library > > > 169 College Avenue, New Brunswick, NJ 08901 > > > > > > http://rucore.libraries.rutgers.edu/ > > > > > >
Re: [CODE4LIB] COinS metadata format support
Mike, I initially started with microdata; larger coverage... Someone reminded me about COinS and that has gotten me distracted now. Been weighing both back and forth in my mind. Why not both? Can I have my cake and eat it too? I like cake, Chad - Original Message - From: "Michael J. Giarlo" To: CODE4LIB@LISTSERV.ND.EDU Sent: Friday, January 17, 2014 1:33:45 PM Subject: Re: [CODE4LIB] COinS metadata format support Chad, In that case, I wonder if you might get more mileage out of schema.orgmicrodata instead of COinS. There are undoubtedly more clients out there that can make sense of HTML5 microdata than COinS, which is really showing its age and is a niche technology. -Mike On Fri, Jan 17, 2014 at 10:25 AM, Chad Mills wrote: > Jodi, > > No. I am working with our repository resources which is an eclectic > mixture of resource types. I just want to simply embed our metadata in our > search results and record displays for other tools to use. It seems cheap > and reasonable to do I just didn't want to limit this feature to only > certain resource types. > > Best, > Chad > > > - Original Message - > From: "Jodi Schneider" > To: CODE4LIB@LISTSERV.ND.EDU > Sent: Friday, January 17, 2014 12:54:43 PM > Subject: Re: [CODE4LIB] COinS metadata format support > > Hi Chad, > > Are these subscription images/video/audio that libraries have? The original > purpose of COinS, as I understand it, was to get people to subscription > copies. Depending on what you're doing (i.e. the purpose/intended use) > there might be a better standard these days. > > In case it helps there's more info here: > http://ocoins.info/ > (though it looks like the generator isn't up any longer, maybe due to "OCLC > New Jersey" hosting?) > > Hopefully you'll get some more helpful advice from others! > > -Jodi > > > > > On Fri, Jan 17, 2014 at 5:36 PM, Chad Mills > wrote: > > > I was able to easily find and create COinS for books and journals. I > > started thinking about images, video, audio, etc. I see references to > > 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value some places. I > would > > assume if I went down that road the rft.genre would have a value of > > 'unknown' as well. Is there some other alternative I am missing when > > handling other formats? > > > > Thanks! > > > > -- > > Chad Mills > > Digital Library Architect > > Ph: 848.932.5924 > > Fax: 848.932.1386 > > Cell: 732.309.8538 > > > > Rutgers University Libraries > > Scholarly Communication Center > > Room 409D, Alexander Library > > 169 College Avenue, New Brunswick, NJ 08901 > > > > http://rucore.libraries.rutgers.edu/ > > >
Re: [CODE4LIB] COinS metadata format support
Is there an easy-to-use tool for schema.org microdata? I was fond of the OCLC NJ COinS tool, but it has gone. Anything of that ilk? Thanks, Dave -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Michael J. Giarlo Sent: Friday, January 17, 2014 12:34 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] COinS metadata format support Chad, In that case, I wonder if you might get more mileage out of schema.orgmicrodata instead of COinS. There are undoubtedly more clients out there that can make sense of HTML5 microdata than COinS, which is really showing its age and is a niche technology. -Mike On Fri, Jan 17, 2014 at 10:25 AM, Chad Mills wrote: > Jodi, > > No. I am working with our repository resources which is an eclectic > mixture of resource types. I just want to simply embed our metadata > in our search results and record displays for other tools to use. It > seems cheap and reasonable to do I just didn't want to limit this > feature to only certain resource types. > > Best, > Chad > > > - Original Message - > From: "Jodi Schneider" > To: CODE4LIB@LISTSERV.ND.EDU > Sent: Friday, January 17, 2014 12:54:43 PM > Subject: Re: [CODE4LIB] COinS metadata format support > > Hi Chad, > > Are these subscription images/video/audio that libraries have? The > original purpose of COinS, as I understand it, was to get people to > subscription copies. Depending on what you're doing (i.e. the > purpose/intended use) there might be a better standard these days. > > In case it helps there's more info here: > http://ocoins.info/ > (though it looks like the generator isn't up any longer, maybe due to > "OCLC New Jersey" hosting?) > > Hopefully you'll get some more helpful advice from others! > > -Jodi > > > > > On Fri, Jan 17, 2014 at 5:36 PM, Chad Mills > wrote: > > > I was able to easily find and create COinS for books and journals. > > I started thinking about images, video, audio, etc. I see > > references to 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value > > some places. I > would > > assume if I went down that road the rft.genre would have a value of > > 'unknown' as well. Is there some other alternative I am missing > > when handling other formats? > > > > Thanks! > > > > -- > > Chad Mills > > Digital Library Architect > > Ph: 848.932.5924 > > Fax: 848.932.1386 > > Cell: 732.309.8538 > > > > Rutgers University Libraries > > Scholarly Communication Center > > Room 409D, Alexander Library > > 169 College Avenue, New Brunswick, NJ 08901 > > > > http://rucore.libraries.rutgers.edu/ > > >
Re: [CODE4LIB] COinS metadata format support
Chad, In that case, I wonder if you might get more mileage out of schema.orgmicrodata instead of COinS. There are undoubtedly more clients out there that can make sense of HTML5 microdata than COinS, which is really showing its age and is a niche technology. -Mike On Fri, Jan 17, 2014 at 10:25 AM, Chad Mills wrote: > Jodi, > > No. I am working with our repository resources which is an eclectic > mixture of resource types. I just want to simply embed our metadata in our > search results and record displays for other tools to use. It seems cheap > and reasonable to do I just didn't want to limit this feature to only > certain resource types. > > Best, > Chad > > > - Original Message - > From: "Jodi Schneider" > To: CODE4LIB@LISTSERV.ND.EDU > Sent: Friday, January 17, 2014 12:54:43 PM > Subject: Re: [CODE4LIB] COinS metadata format support > > Hi Chad, > > Are these subscription images/video/audio that libraries have? The original > purpose of COinS, as I understand it, was to get people to subscription > copies. Depending on what you're doing (i.e. the purpose/intended use) > there might be a better standard these days. > > In case it helps there's more info here: > http://ocoins.info/ > (though it looks like the generator isn't up any longer, maybe due to "OCLC > New Jersey" hosting?) > > Hopefully you'll get some more helpful advice from others! > > -Jodi > > > > > On Fri, Jan 17, 2014 at 5:36 PM, Chad Mills > wrote: > > > I was able to easily find and create COinS for books and journals. I > > started thinking about images, video, audio, etc. I see references to > > 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value some places. I > would > > assume if I went down that road the rft.genre would have a value of > > 'unknown' as well. Is there some other alternative I am missing when > > handling other formats? > > > > Thanks! > > > > -- > > Chad Mills > > Digital Library Architect > > Ph: 848.932.5924 > > Fax: 848.932.1386 > > Cell: 732.309.8538 > > > > Rutgers University Libraries > > Scholarly Communication Center > > Room 409D, Alexander Library > > 169 College Avenue, New Brunswick, NJ 08901 > > > > http://rucore.libraries.rutgers.edu/ > > >
Re: [CODE4LIB] COinS metadata format support
Mike, Basically embedding metadata on resource pages and result lists for other tools to pickup. I would probably build off of it for other *things* that are yet to be determined. -Chad - Original Message - From: "Michael J. Giarlo" To: CODE4LIB@LISTSERV.ND.EDU Sent: Friday, January 17, 2014 1:05:29 PM Subject: Re: [CODE4LIB] COinS metadata format support What's your use case for the COinS, Chad? -Mike On Fri, Jan 17, 2014 at 10:00 AM, Karen Coyle wrote: > The missing formats are missing because they were never defined in the > OpenURL standard. There is a registry of formats [1] that was designed to > be updatable, although few updates have been done. I worked on the document > type standards that are there today, and would happily help develop > additional types if we can get some assurance that they could be added to > the standard. I honestly do not know what mechanism exists for adding new > types, but if anyone is interested we could ping the appropriate folks at > OCLC and see. > > kc > [1] http://alcme.oclc.org/openurl/servlet/OAIHandler?verb= > ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats > > > On 1/17/14, 8:36 AM, Chad Mills wrote: > >> I was able to easily find and create COinS for books and journals. I >> started thinking about images, video, audio, etc. I see references to >> 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value some places. I would >> assume if I went down that road the rft.genre would have a value of >> 'unknown' as well. Is there some other alternative I am missing when >> handling other formats? >> >> Thanks! >> >> -- >> Chad Mills >> Digital Library Architect >> Ph: 848.932.5924 >> Fax: 848.932.1386 >> Cell: 732.309.8538 >> >> Rutgers University Libraries >> Scholarly Communication Center >> Room 409D, Alexander Library >> 169 College Avenue, New Brunswick, NJ 08901 >> >> http://rucore.libraries.rutgers.edu/ >> > > -- > Karen Coyle > kco...@kcoyle.net http://kcoyle.net > m: 1-510-435-8234 > skype: kcoylenet >
Re: [CODE4LIB] COinS metadata format support
Jodi, No. I am working with our repository resources which is an eclectic mixture of resource types. I just want to simply embed our metadata in our search results and record displays for other tools to use. It seems cheap and reasonable to do I just didn't want to limit this feature to only certain resource types. Best, Chad - Original Message - From: "Jodi Schneider" To: CODE4LIB@LISTSERV.ND.EDU Sent: Friday, January 17, 2014 12:54:43 PM Subject: Re: [CODE4LIB] COinS metadata format support Hi Chad, Are these subscription images/video/audio that libraries have? The original purpose of COinS, as I understand it, was to get people to subscription copies. Depending on what you're doing (i.e. the purpose/intended use) there might be a better standard these days. In case it helps there's more info here: http://ocoins.info/ (though it looks like the generator isn't up any longer, maybe due to "OCLC New Jersey" hosting?) Hopefully you'll get some more helpful advice from others! -Jodi On Fri, Jan 17, 2014 at 5:36 PM, Chad Mills wrote: > I was able to easily find and create COinS for books and journals. I > started thinking about images, video, audio, etc. I see references to > 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value some places. I would > assume if I went down that road the rft.genre would have a value of > 'unknown' as well. Is there some other alternative I am missing when > handling other formats? > > Thanks! > > -- > Chad Mills > Digital Library Architect > Ph: 848.932.5924 > Fax: 848.932.1386 > Cell: 732.309.8538 > > Rutgers University Libraries > Scholarly Communication Center > Room 409D, Alexander Library > 169 College Avenue, New Brunswick, NJ 08901 > > http://rucore.libraries.rutgers.edu/ >
Re: [CODE4LIB] COinS metadata format support
What's your use case for the COinS, Chad? -Mike On Fri, Jan 17, 2014 at 10:00 AM, Karen Coyle wrote: > The missing formats are missing because they were never defined in the > OpenURL standard. There is a registry of formats [1] that was designed to > be updatable, although few updates have been done. I worked on the document > type standards that are there today, and would happily help develop > additional types if we can get some assurance that they could be added to > the standard. I honestly do not know what mechanism exists for adding new > types, but if anyone is interested we could ping the appropriate folks at > OCLC and see. > > kc > [1] http://alcme.oclc.org/openurl/servlet/OAIHandler?verb= > ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats > > > On 1/17/14, 8:36 AM, Chad Mills wrote: > >> I was able to easily find and create COinS for books and journals. I >> started thinking about images, video, audio, etc. I see references to >> 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value some places. I would >> assume if I went down that road the rft.genre would have a value of >> 'unknown' as well. Is there some other alternative I am missing when >> handling other formats? >> >> Thanks! >> >> -- >> Chad Mills >> Digital Library Architect >> Ph: 848.932.5924 >> Fax: 848.932.1386 >> Cell: 732.309.8538 >> >> Rutgers University Libraries >> Scholarly Communication Center >> Room 409D, Alexander Library >> 169 College Avenue, New Brunswick, NJ 08901 >> >> http://rucore.libraries.rutgers.edu/ >> > > -- > Karen Coyle > kco...@kcoyle.net http://kcoyle.net > m: 1-510-435-8234 > skype: kcoylenet >
Re: [CODE4LIB] COinS metadata format support
The missing formats are missing because they were never defined in the OpenURL standard. There is a registry of formats [1] that was designed to be updatable, although few updates have been done. I worked on the document type standards that are there today, and would happily help develop additional types if we can get some assurance that they could be added to the standard. I honestly do not know what mechanism exists for adding new types, but if anyone is interested we could ping the appropriate folks at OCLC and see. kc [1] http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats On 1/17/14, 8:36 AM, Chad Mills wrote: I was able to easily find and create COinS for books and journals. I started thinking about images, video, audio, etc. I see references to 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value some places. I would assume if I went down that road the rft.genre would have a value of 'unknown' as well. Is there some other alternative I am missing when handling other formats? Thanks! -- Chad Mills Digital Library Architect Ph: 848.932.5924 Fax: 848.932.1386 Cell: 732.309.8538 Rutgers University Libraries Scholarly Communication Center Room 409D, Alexander Library 169 College Avenue, New Brunswick, NJ 08901 http://rucore.libraries.rutgers.edu/ -- Karen Coyle kco...@kcoyle.net http://kcoyle.net m: 1-510-435-8234 skype: kcoylenet
Re: [CODE4LIB] COinS metadata format support
Hi Chad, Are these subscription images/video/audio that libraries have? The original purpose of COinS, as I understand it, was to get people to subscription copies. Depending on what you're doing (i.e. the purpose/intended use) there might be a better standard these days. In case it helps there's more info here: http://ocoins.info/ (though it looks like the generator isn't up any longer, maybe due to "OCLC New Jersey" hosting?) Hopefully you'll get some more helpful advice from others! -Jodi On Fri, Jan 17, 2014 at 5:36 PM, Chad Mills wrote: > I was able to easily find and create COinS for books and journals. I > started thinking about images, video, audio, etc. I see references to > 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value some places. I would > assume if I went down that road the rft.genre would have a value of > 'unknown' as well. Is there some other alternative I am missing when > handling other formats? > > Thanks! > > -- > Chad Mills > Digital Library Architect > Ph: 848.932.5924 > Fax: 848.932.1386 > Cell: 732.309.8538 > > Rutgers University Libraries > Scholarly Communication Center > Room 409D, Alexander Library > 169 College Avenue, New Brunswick, NJ 08901 > > http://rucore.libraries.rutgers.edu/ >
[CODE4LIB] COinS metadata format support
I was able to easily find and create COinS for books and journals. I started thinking about images, video, audio, etc. I see references to 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value some places. I would assume if I went down that road the rft.genre would have a value of 'unknown' as well. Is there some other alternative I am missing when handling other formats? Thanks! -- Chad Mills Digital Library Architect Ph: 848.932.5924 Fax: 848.932.1386 Cell: 732.309.8538 Rutgers University Libraries Scholarly Communication Center Room 409D, Alexander Library 169 College Avenue, New Brunswick, NJ 08901 http://rucore.libraries.rutgers.edu/
