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:[log in to unmask]] On Behalf Of Chad Mills
Sent: Friday, January 17, 2014 1:46 PM
To: [log in to unmask]
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" <[log in to unmask]>
To: [log in to unmask]
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 <[log in to unmask]>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" <[log in to unmask]>
> To: [log in to unmask]
> 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 <[log in to unmask]>
> 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/
> >
>