author Denis Laxalde <>
Tue, 20 Feb 2018 10:12:22 +0100
changeset 2950 960c8c66cfc2
parent 2937 dec8827e705f
child 2952 f30a729c4a9d
permissions -rw-r--r--
Rely on cubicweb-skos's extid2eid mapping during LCSV data import We drop monkeypatches and hacks introduced in 49d118aa8254 in 2016 which were supposed to be transient waiting for a cubicweb-skos release which came a long time ago now. Now we build the extid2eid dict before importing LCSV concept schemes and pass it to store_skos_extentities() so that it will be re-used for all files instead of re-built. Both lcsv_import and lcsv_check functions are updated, as the latter is used in as a kind of "mock" but must respect the former's interface. Also note that we now have to update 'extid2eid' dict after creating a new concept scheme (with init_seda_scheme()): while this sounds perfectly reasonable, I don't completely understand how this works without this before... We update requirement on cubicweb-skos so that the latest release is used (though some previous release would probably work as well, but I'm not sure which and it's not so easy to test).

# pylint: disable=W0622
"""cubicweb-seda application packaging information"""

modname = 'seda'
distname = 'cubicweb-seda'

numversion = (0, 13, 1)
version = '.'.join(str(num) for num in numversion)

license = 'LGPL'
author = 'LOGILAB S.A. (Paris, FRANCE)'
author_email = ''
description = 'Data Exchange Standard for Archival'
web = '' % distname

__depends__ = {
    'cubicweb': '>= 3.25.4, < 3.27',
    'six': '>= 1.4.0',
    'cubicweb-eac': None,
    'cubicweb-skos': '>= 1.3.0',
    'cubicweb-compound': '>= 0.7',
    'cubicweb-relationwidget': '>= 0.4',
    'cubicweb-squareui': None,
    'pyxst': '>= 0.2',
    'rdflib': '>= 4.1',
__recommends__ = {}

classifiers = [
    'Environment :: Web Environment',
    'Framework :: CubicWeb',
    'Programming Language :: Python',
    'Programming Language :: JavaScript',