Release 86
----------

ECIMPORTER: 1.1.5 (new)
* DB-migration: no
* ini-file: no
* others: no

Release 68
----------

ECIMPORTER: 1.1.4 (new)
* DB-migration: no
* ini-file: yes
* others: no

!!! IMPORTANT !!!

To retain functionality
we have to "fake" identity of
service as "derived from ec"

add

app.base = ec

to development.ini

See development.ini.example

!!! IMPORTANT !!!


Release 67
----------

ECIMPORTER: 1.0.2
* DB-migration: yes
* ini-file: no
* others: no

Release 51
----------

ECIMPORTER: 1.0.1
* DB-migration: no
* ini-file: no
* others: no

Release 48 - IN DEVELOPMENT
---------------------------
ECIMPORTER: 1.0.0

TODO: Add requirements

Additional steps:
* DB-migration: no
* ini-file: yes

    # Configure the path to the json file created under other changes.
    ecimporter.bearbeiter.maps = /path/to/json/file

    # Configure the min and max ages allowed with the values from EC:
    efa.minage = 15
    efa.maxage = 65

* Other changes:
    The JSON file referenced above maps the user on BEWEC to a user on the
    EC side, as well as the groups. Applications transfered from BEWEC will
    belong to this user.

    The expected format of the file is the following:
    {
        "bearbeiter_to_uid": {"<bewec-id1>": "<ec-id2>", [...]}
        "bearbeiter_to_gid": {"<bewec-id1>": "<ec-id3>", [...]}
    }

    The mapping can be generated with the results produced by the following
    commands:

    -- BEWEC
    -- this list is the <bewec-id1> in the example above
    SELECT bearbeiter FROM applications;


    -- EC
    -- map the <bewec-ids> from the example above to a user or users of your
    -- choice on an EC system
    SELECT u.id AS user_id, g.id AS group_id, u.login AS username FROM users AS u JOIN usergroups AS g on u.login = g.name;