Re: [Invenio] #579: dbdump: dump only certain tables

[Invenio Trac]

#579: dbdump: dump only certain tables
--+--
  Reporter:  simko|  Owner:  rajimene
  Type:  enhancement  | Status:  in_merge
  Priority:  major|  Milestone:
 Component:  MiscUtil |Version:
Resolution:   |   Keywords:
--+--
Changes (by rajimene):

 * status:  in_work => in_merge


-- 
Ticket URL: 
Invenio 

Re: [Invenio] #158: BibSched erroneously thinks that tasks failed to run

[Invenio Trac]

#158: BibSched erroneously thinks that tasks failed to run
---+--
  Reporter:  skaplun   |  Owner:  skaplun
  Type:  defect| Status:  assigned
  Priority:  critical  |  Milestone:
 Component:  BibSched  |Version:
Resolution:|   Keywords:
---+--

Comment (by Tibor Simko ):

 In [7038029ac01a266db710492ea2277a019d7441d4]:
 {{{
 #!CommitTicketReference repository=""
 revision="7038029ac01a266db710492ea2277a019d7441d4"
 BibSched: use larger timouts for launching tasks

 * When launching or waking up tasks, use larger timeout before
   checking whether the task was well launched.  This works around
   problems like slow loading of large citation dictionaries.
   (addresses #158)
 }}}

-- 
Ticket URL: 
Invenio 

Re: Invenio and INSPIRE code swarm movie

[Ferran Jorba]

Hello Tibor and Samuele,

> Il giorno lun, 18/04/2011 alle 13.46 +0200, Tibor Simko ha scritto: 
>> As we have discussed some weeks ago, here are two short animations with
>> visual representation of Invenio and INSPIRE commit history:
>> 
>>
>>
>
> what tool have you used to generate these? Is it Gource?
> 

It seems to me that it is code_swarm, right?

 http://code.google.com/p/codeswarm/

Thanks for sharing it, Tibor.  I've been imagining many possibilities
since: processing Apache logs, with the names being either the
collections or the submitters, collection growth (with different
variations data from either sbmSUBMISSIONS or bibrec tables, maybe
crossing it with guess_primary_collection_of_a_record), etc. etc.

But wandering at the http://www.michaelogawa.com/research/ site, I feel
that the evolines (or storylines) visualisation prototype is also
fascinating:

 http://www.michaelogawa.com/research/storylines/

Ars longa, vita brevis,

Ferran

[Invenio] #623: Replace FCKeditor with CKEditor

[Invenio Trac]

#623: Replace FCKeditor with CKEditor
--+--
 Reporter:  jcaffaro  |  Owner:  jcaffaro
 Type:  task  | Status:  new
 Priority:  major |  Milestone:
Component:  MiscUtil  |Version:
 Keywords:|
--+--
 As described in Savannah task
 [https://savannah.cern.ch/task/?func=detailitem&item_id=11267  #112]:
 > 2009-09-18 12:02, original submission, submitted by Jerome Caffaro:
 > FCKeditor has been updated and renamed to CKEditor. Upgrading to the new
 package will be necessary.
 > Transition should be quite easy.
 > http://ckeditor.com/


 CKEditor removed the native support for Python server-side integration
 (including the "quick uploader"). Since we have already moved to
 Javascript-based integration, it only remains to provide the interface to
 upload files using the editor. This ''might'' be simpler than expected:
 http://alfonsoml.blogspot.com/2009/12/using-your-own-uploader-in-
 ckeditor.html

-- 
Ticket URL: 
Invenio 

Re: [Invenio] #604: bibknowledge needs updates to better support autocomplete

[Invenio Trac]

#604: bibknowledge needs updates to better support autocomplete
---+--
  Reporter:  jblayloc  |  Owner:  jblayloc
  Type:  defect| Status:  in_merge
  Priority:  major |  Milestone:
 Component:  BibKnowledge  |Version:
Resolution:|   Keywords:  review:simko
---+--
Changes (by jblayloc):

 * keywords:  review:skaplun => review:simko
 * status:  assigned => in_merge


Comment:

 I have made another commit on this branch which addresses all of Sam's
 concerns and also extends the API in a way necessary to Mike's citation
 mode project.  All of the regression tests (old and new) and kwalitee
 checks pass.  It is available on both my github, and my AFS space, on the
 same branchname '604-bibknowledge_autocomplete_improvement'.

 Sam, if you want to change to using 'json' for your rest api calls now
 would be a good time.  You don't have to though; 'jquery' will continue to
 work.

 I think it's ready for merge.

-- 
Ticket URL: 
Invenio 

Re: [Invenio] #604: bibknowledge needs updates to better support autocomplete

[Invenio Trac]

#604: bibknowledge needs updates to better support autocomplete
---+
  Reporter:  jblayloc  |  Owner:  jblayloc
  Type:  defect| Status:  assigned
  Priority:  major |  Milestone:
 Component:  BibKnowledge  |Version:
Resolution:|   Keywords:  review:skaplun
---+

Comment (by jblayloc):

 To be clear about the impact on, e.g., BibEdit: There should be no impact
 for two reasons:
 1. I don't think I changed anything that will be visible to BibEdit (as I
 mention above) and
 2. Autocomplete in BibEdit is currently broken anyway. :)

-- 
Ticket URL: 
Invenio