>>> So, it is nice that one can download the html.
>>> It links to data in citeline.
>>>
>>> But suppose somebody wanted to source the feed from their bibtex file on
>>> the web, so they can keep it up to date without going back to
>>> citeline?
>>>
>> Then you download the exhibit json (using the handy little scissor
>> thing), put the json with the html,
>> and edit the html with the new data path. Voila, encore:
>>
>> http://web.mit.edu/kenzie/www/david%27s_bibliography.html
>>
> no, that would make a _new_ source file of json, and if they changed
> their bibtex, the exhibit wouldn't change. that's why I suggested
> sourceing the feed directly from the bibtex, using a trick like babel.
>
I guess this boils down to where you want to maintain your bibliographic
data...
-- in a tool custom-built for that purpose (endnote, zotero)
-- in Citeline
-- in a JSON file on your Web server
I think you're proposing another scenario: arbitrary Web location that
is *not* your Web site (or anyway not the JSON you exported from Citeline).
Agreed that users will prefer to maintain bibtex in some format other
than Exhibit JSON.
Disagree that this constitutes a common enough scenario to worry much
about... most of our users are in endnote/refworks/zotero.
If they weren't almost all using bibliographic management tools already,
then we would have designed the tool quite differently.
MacKenzie
Received on Fri Sep 26 2008 - 18:27:53 EDT