#314: CV generator
--------------------------+--------------------------------------
Reporter: tbrooks | Owner: valkyrie
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: BibFormat | Version:
Resolution: | Keywords: INSPIRE formats DEPLOYED
--------------------------+--------------------------------------
Changes (by simko):
* status: closed => new
* resolution: fixed =>
Comment:
Replying to [comment:26 jblayloc]:
> It's in inspire-ops, commit 77b482e73e087a58831cb50012717c84c41f375e
This commit uses hard coded format names 'hcv', 'htcv', 'tlcv' that do not
come with the commit, in spite of the commit log message. So the commit
is incomplete. Moreover, the format names being hard coded, but not
coming with the commit, this could result in a conflict with an Invenio
installation that uses the same output format names for other stuff.
We should either (1) include these formats together with this commit into
upstream Invenio (like the hcs format is), customised towards Atlantis
demo site conditions, which would permit is to write test cases and stuff,
and which would permit other Invenio installations to re-use this format.
Or we should (2) use special CV actions for these hard-coded format names
only when the CFG_INSPIRE_SITE flag is on, so that no other Invenio
installation would get perturbed. (In which case the
`search_engine_cvifier.py` file would not even have to be included with
the upstream Invenio sources.)
Note that the patch you mention does a bit of both approaches, since it
commits some parts to Invenio and some parts to INSPIRE, but the parts are
not completely consistent. Se need to clean the patch before merging,
either in one direction or the other.
--
Ticket URL: <http://invenio-software.org/ticket/314#comment:31>
Invenio <http://invenio-software.org>
