imDbAnonymizer

Tool to anonymize data in mariadb
Report bugs · Request Feature

Table of Content

• About
• Geting started
• Configuration
• About me and us

About

This is an application made for KoHa. However it should not be a problem,
using it for other programs; Primarily, because it is very customizable.

Geting started

So, first of all this is a java application, and it uses mvn to compile.
This means that you are expected to know a little about java and mvn to
be able to compile and use this application. You are also expected to
understand a bit about xml to be able to configure it.
If this is not so, dont fear; As you are able to get help by us "imCode", should
you chose to.

Now that that is out of the way, lets get in to how to use it. First
you will have to install the code.

git clone https://github.com/imCodePartnerAB/imDbAnonymizer

Ok so now that this is done, we will have to compile the program.

cd imDbAnonymizer
mvn package

You should now have a file in target/imAnonymizer-jar-with-dependencies.jar.
This will be the file to execute.
However if you run it now you will get an error:

#>java -jar  target/imAnonymizer-jar-with-dependencies.jar
-- 2020/08/12 17:46:53 - Starting
-- 2020/08/12 17:46:53 - Parsing failed.  Reason: Missing required option: xmlfile
usage: imAnonymizer
    --xmlfile <file>   Use this xmlfile to run.
-- 2020/08/12 17:46:53 - java.lang.NullPointerException
--      at com.imcode.internal.imAnonymizer.parser.Value.getJdbcURl(Value.java:43)
--      at com.imcode.internal.imAnonymizer.db.connect(db.java:31)
--      at com.imcode.internal.imAnonymizer.db.<init>(db.java:23)
--      at com.imcode.internal.imAnonymizer.Main.main(Main.java:31)
--
Exception in thread "main" java.lang.NullPointerException
        at com.imcode.internal.imAnonymizer.Main.main(Main.java:33)

If you look closely you will notice that it complains about not having a
parameter --xmlfile. And this is when we move to the next session
configuration.

Configuration

The configuration works by editing the XML file, and you will also use
resource files. The resource files will contain lines that will be
randomly chosen and inserted in the database, in the field you chose.

The template/example files are located in src/non-packaged-resources
and if we open src/non-packaged-resources/vikingfname.txt we will
se that this contains a lot of rows with different sir names.

If we now open src/non-packaged-resources/example.xml we can start
putting it together. First of all there is a section where you have
to set your database you want to change. (We will not be responsible
for any destroyed data, so make sure you do this with a test database)

You can chose to just print the SQL you need to the console, and/or
you can chose to update the database directly.

The example database is preconfigured for KoHa library system, however
we will look att the config and how you can configure it to fit your
needs.

Now then, the first section is this is where you configure
the files and templates you want to call for your different tables and
fields. You can configure with you want to use further
down and with the which should contain the filename to use.

You will also be able to configure fields in this
section. A field will contain a you want to call
further down and the (NULL) is a valid option here if you
want nothing in fields calling this .

Now we are geting to the and subtree

which contains your
configuration that maps the above to the correct table and
field.

For each

you will need to configure , , and also
the subtree . The tree contains which is the
section containing each specific table field. Here you will need to set
the and , where value is the alias you configure above.

Example:

    <tables>
        <!-- Here you specify the tables,
        <table>
            <name>issues</name>
            <idfield>issue_id</idfield>
            <fields>
                <field>
                    <name>note</name>
                    <if>notempty</if>
                    <value>ipsum</value>
                </field>
            </fields>
        </table>
    </tables>

Here you see that in the table issues, which has the idfield issue_id, we
will insert the value of ipsum if it is notempty else it will not
change the value from empty.

I hope this explanation is understandable, but feel free to give me any
pointers on how to make it more understandable.

About me and us

I work for imCode AB which is a Swedish company specialized in advanced
web-services, mostly for big organizations and municipalities services.

Here I work mainly as system developer and most of my time is managing
servers and applications running on these. From time to time I also get
to work with system level programming and other programming to make
life easier for customers and our other interface developers. I am far
from a interface developer so I gladly keep in the background. Don't think
I could make a good interface to save my life :)

However if you contact me with a case or request we have very competent
people both in our office in Sweden and abroad; And I would love to help
anyone with their idea or request, and even if I'm not the man for the job
im sure I would be able to find the right person for your case. If it is
internet service/application related of course.