#823: Inspire bibtex creation
---------------------------+------------------------
Reporter:  annetteh        |       Owner:
    Type:  defect          |      Status:  new
Priority:  major           |   Component:  BibUpload
 Version:                  |  Resolution:
Keywords:  Inspire bibtex  |
---------------------------+------------------------

Comment (by simko):

 Adding December 2011 musings from the inspire-dev mailing list:

 {{{
 The daemon option sounds good to me - if we can avoid adding texkeys
 to arxiv records directly harvested to Inspire since these will be
 overwritten the next day by texkeys generated in spires. And we agreed
 that texkeys should be stable.

 Annette

 On Dec 16, 2011, at 11:51 AM, Tibor Simko wrote:
 > On Thu, 15 Dec 2011, Joe Blaylock wrote:
 >> I've been meaning to ask you about that.  It would be very nice if this
 >> could just happen inside bibupload.  Is there a clean way for bibupload
 >> to support calling out to an external program or routine for metadata
 >> augmentation at upload time?  And if not, can I add one?
 >
 > There is not a clean way yet, because we usually enrich XML files (if
 > need be) at a pre-bibupload step, so that the uploader itself stays
 > simple.  This is easy to do for files coming via harvesting workflow,
 > but it would not very practical to do so for bibedited or robot-uploaded
 > files.
 >
 > So we should either (i) add such a mechanism indeed, or alternatively
 > (ii) we should write a daemon that would run in the background and would
 > scan records that have missing TeX keys and that would generate them
 > properly and would enrich records with them.  The second alternative is
 > akin to how OAI IDs are being generated by the `oairepositoryupdater'
 > daemon.  We could clone it easily for TeX keys as well.
 >
 > BTW, even if we go for the first solution (which enables to have TeX
 > keys being present faster right after the record creation), it may be
 > good to have such a daemon anyway, so that it would check and eventually
 > auto-correct any troubles there may be.  This could give us yet another
 > (iii) hybrid option.
 >
 > But it's probably more practical to simply pick just one option,
 > e.g. the daemon one.
 }}}

-- 
Ticket URL: <http://invenio-software.org/ticket/823#comment:4>
Invenio <http://invenio-software.org>

Reply via email to