Cool project. Where is the data and how was it acquired / what's the provenance? I found this:
Data: We have a bunch of catalog data and fulltext acquired from various sources, either sitting in the Archive or to be uploaded to there. I think the acquisition processes (including web crawling scripts for some of the data) is outside the scope of an Open Library software install. There are a bunch of additional scripts to make the stuff usable in openlibrary and these need to be documented. These include TDB Conversion Scripts written by dbg, and (for OCA fulltext) Archive Spidering and Solr Importing scripts written by phr.
edit: I should add the question: does openlibrary support fulltext search of actual books or fulltext search of the metadata?
If you would like to see the data that's currently in Open library, there are dumps published every month or so. Where the data comes from is either partners or one off projects to scrape from public sources or sometimes just people adding what they like.
Fulltext search of actual books! And also metadata.
If you're serious about getting involved I'd say the best thing to do it just come to the meeting if you can. The GitHub has a lot of things that without context can be hard to pickup. Most of the easy stuff is on the JS side.
Comments
Cool project. Where is the data and how was it acquired / what's the provenance? I found this:
edit: I should add the question: does openlibrary support fulltext search of actual books or fulltext search of the metadata?
If you would like to see the data that's currently in Open library, there are dumps published every month or so. Where the data comes from is either partners or one off projects to scrape from public sources or sometimes just people adding what they like.
Fulltext search of actual books! And also metadata.
Check it out:
https://openlibrary.org/search/inside?q=hackernews
If you're serious about getting involved I'd say the best thing to do it just come to the meeting if you can. The GitHub has a lot of things that without context can be hard to pickup. Most of the easy stuff is on the JS side.