Re: Holdings-as-Offer: more complete examples

Looks Good Dan !

Most importantly... of the Offers, they all can be sub-filtered by the
locations' shelves.  The Google Custom Search structured data testing tool
reveals these among other valuable properties that allow faceting/filtering
:

more:pagemap:offer-availableatorfrom
more:pagemap:offer-availableatorfrom:stacks

more:pagemap:organization
more:pagemap:organization-location
more:pagemap:organization-location:ont
more:pagemap:organization-location:sudbury
more:pagemap:organization-location:sudbury__ont.__
more:pagemap:organization-name
more:pagemap:organization-name:huntington
more:pagemap:organization-name:huntington_university_
more:pagemap:organization-name:university

So that's an immediate win.

Library user asks Search: "But which Offers are at that library closest too
me....what's the name / location of it called again?"  Bam !

Library user  asks Search: "But which Offers near me have that 1977 version
...(NOT the 1999 version)...the one I grew up on"  Bam !

Library user asks Search: "uggh... But which Offers near me have that 1977
version ... That is NOT in the Archives but on the regular shelves for me
to grab easily" Bam!



On Mon, Oct 28, 2013 at 12:39 PM, Dan Scott <denials@gmail.com> wrote:

> Okay. I've updated
> http://www.w3.org/community/schemabibex/wiki/Holdings_via_Offer to use
> "availableAtOrFrom" for shelving location, as that seemed to be the
> consensus from the "Holdings-as-Offer: wrap-up" thread at
> http://www.w3.org/community/schemabibex/wiki/Holdings_via_Offer
>
> What also came out of that thread was an expression of interest in
> seeing more fully fleshed out examples, showing how the "seller"
> property could be connected to a Library in a meaningful sense. I
> mentioned my interest in teaching Evergreen how to express the
> information that it already knows about its libraries (such as opening
> hours, addresses, etc) in such a way that we could link Offer items to
> Library items. And so I did, over the weekend, just that.
>
> You might have seen a sneak preview of this on my G+ post at
> https://plus.google.com/116747292129029460979/posts/XJ749hYz79q , but
> I can now point at an example extracted from an Evergreen system
> running the branch of code I created for this purpose at
> http://stuff.coffeecode.net/schema.org/evergreen/library_schema_copies.html
> . Notice how each of the copies links to the library where that copy
> is currently circulating; for example, "Example Branch 1" lives at
> http://stuff.coffeecode.net/schema.org/evergreen/library/BR1
>
> Feel free to run the Rich Snippets tool or RDFa extraction tools
> against these results. It's a nice beginning, I think, towards turning
> this vision into reality. There's much more to do, of course, but the
> part that really excites me is that a library running Evergreen would
> get this for free - no effort required outside of the normal
> administration operations required to set hours of operation, contact
> info, etc, that already exist (assuming, of course, that this branch
> is polished and eventually accepted into a future Evergreen release).
>
> Note that some of the links on the pages will 404 because I'm not
> running a live Evergreen instance on coffeecode.net; I just captured
> some HTML that was generated from the branch running on my laptop and
> adjusted a few of the URLs to pull in the CSS, etc, so that it didn't
> look quite as ugly to humans.
>
> Feedback more than welcome!
>
>


-- 
-Thad
Thad on Freebase.com <http://www.freebase.com/view/en/thad_guidry>
Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/>