the book it's in is crazy huge, it's like ... bound A-4 plus margins, or something? Maybe it's a B size or something, I don't know
in the case of this particular paper, it's only marginally important, because the paper that's readily available (the one that cites it in that editgroup above) is strictly superior and describes the entire algorithm ... but of course I didn't know that until I found the paper
if you mail it in to us (donate, won't get it back), we will scan it and lend via openlibrary.org. though if it is a weird size it will probably sit in the queue for a while, and the process always takes at least a few months
looking at 3-D renderings of CAD parts as 1977 state of the art, admiring hand-lettered equations and graphs, etc. :-)
and even if we allow that copyright has a place and we consider that current publications are just a matter of belonging to some University library or something (a different discussion), in cases like this the publisher is either gone or doesn't care any more
so like ... the one billion articles my University library has access to don't include this volume
@bnewbold: so I've found a conference that's very influential, the Winter 1990 USENIX (the original Tcl paper was published there, for example), but it doesn't have a Wikidata QID, it doesn't have an ISSN (that I can find), the papers in it don't seem to have DOIs ... what should/could I do with this?
I'm entering the Tcl paper right now, which has crappy entries in citeseer/dblp/etc. (the fatcat entry will be more complete when I'm done with it in some ways!), but I'm not sure how to handle the container
hah, our copy in archive.org seems like a complete official run! funny that I didn't know about that
for the "Winter 1990 USENIX", i'd be tempted to use a general "USENIX Conference" container to start, and maybe put "Winter 1990 Proceedings" in the volume field? though it will not display or "cite" with the correct proceedings. creating a container for that specific proceeding is also reasonable though
I am really excited to start having these discussions and have the schema/guide evolve over time and represent a community consensus
a new "container groups" / "container series" entity type is one future path; or containers could be nested; or containers could have a "series" string name; or releases could have a "container_event_name"; etc
or maybe both the "series" and "event" containers could be container entities, and releases could have two relationships, one "container_id" (implied series) and one "event_id" (implied event)
(I didn't want to hit edit on the other, I'm not sure what the status of it is)
Today we upgraded https://search.fatcat.wiki from elasticsearch 6.x to 7.10. everything is mostly compatible, but anybody using this pseudo-supported service directly should be aware of two quirks:
query "total hits" are now a rough estimate by default. the most common symptom of this is total hits being 10,000. you can add the query parameter "track_total_hits" to get the old behavior
total hits were previously an integer in the JSON response. now there is an extra layer of JSON object, with the integer at the key 'value'
also, previously each index had document types; these were deprecated and all documents within an index have the same type, and are all "_doc" for all indices
hi! I've been looking for software or a service to manage annotated bibliographies for a web site, but having trouble figuring out whether there's anything that quite works the way I imagine
sort or select by date or keyword or genre (book, reference manual, paper, software/language); include abstracts when available, links to internet archive of actual paper or book when available (or publisher's landing page)
i have discoveed zotero which seems to be quite wonderful for this.
I don't have established functions for selection by date/keyword/genre (although it would be easy with org tags), but I essentially have one outline heading (at level 5, I think, for categories above that) for each work that I'm citing, and that outline heading includes one or more BibTex entries, a URL to the work, a link to a local copy, cross-references to other works in the database as links that can be followed, and notes on the work
some works appear in more than one place with a cross-reference to their canonical location
it's not a database, so there's some room for schema errors to creep in, but since no single file contains more than a hundred or so entries it's manageable