purging un-needed preconfiguration?

Folks;

getting started trying to adopt scarab as our local issue tracker, I am
currently dealing with the fact that most of the preconfigured things
(issues, modules, ...) aren't quite what I need. So, questions:

- Is there a simple way of building / installing scarab having the
database filled with nothing but, say, an administrator user but no
modules, attributes, ticket types, ... ? My problem is that, in my
case, I have to manually create most of the issue types / attributes
anyhow as the system should be used internally by persons not familiar
with the English language, so I have to re-create attributes using
German terminology. 

- Likewise, in the process of getting acquainted to things (read:
playing around), is there a way to, given something so far isn't how I
wanted it to be, completely purge issues, modules, tickets, ticket
types, ... off the db (i.o.w. not just marking them "deleted")? I know
that this basically violates the idea of "traceability" in an issue
tracker yet at least given we're talking about pre-productive adoption
this would utterly helpful.

- As an alternative, running a testbed and a production installation,
is there an easy way of transferring special "items" (ticket types,
attributes, roles, modules, but not tickets itself) between the two of
them? I don't want to have my "experimental" / test tickets floating
all around messing things up...

Thanks in advance and best regards,
Kristian