[open-bibliography] Inviting community engagement on building a bibliographic roadmap

[Thomas Krichel]

  Tom Johnson writes

> I've had pretty good luck with it. We're trying to use this data to do some
> auto-filling during submission to our repository. It's not perfect, but I'd
> certainly rate it useful.
> 
> This is a pretty typical response:
> 
> $ curl -LH "Accept: text/turtle" http://dx.doi.org/10.3852/07-203

  ok that's DOI data. It's cumbersome to deal with, from my 
  experience. But what you have here is data you resolve when
  you know a DOI. But you never get a list of DOIs fulfilling
  a certain criteria. This is what sigg comes in, but as its
  home page suggests

  In the AuthorClaim use case, I want to know more about 
  documents claimed by authors. I create automated queries
  to sigg and submit them. So, if the paper has

Title: foo with bar
Author: Krichel
Auhtor: Yakovenko

  I can query sigg with "Krichel foo", "Yakovenko bar" etc.  That's
  what my software does. It is supposed to run in a self-contained
  fashion on the set of AuthorClaim data, using accessed and refused
  paper metadata. It has heavily home-grown method to find what terms
  to put into the query.

  Cheers,

  Thomas Krichel                    http://openlib.org/home/krichel
                                      http://authorprofile.org/pkr1
                                               skype: thomaskrichel