Best Practices in Managing Properties exposed to User

Hi,

Developing a proof of concept tool for a materials R&D client to create a knowledge map.

Looking at a tool to move client off of Excel spreadsheets and the like.

The like the Bloom interface and one thing that I would like to better advise on is the ability to let the user create new properties. In principle this is extremely valuable especially in an R&D environment. No the downside, I have found that once a property has been created, it can never be removed with resorting to rebuilding the database.

Please, Please correct me if I am wrong here.

This risks inadvertent errors in labels and datatype designation. Are there known technics that a "librarian/admin" could go in and fix error associated with properties? Just copying the value to another property is not sufficient since the old property still exists in generated menus etc. I need the errors gone completely.
It is my impression that this has been a weak point for Neo4J but I am interested in current status.
Andy

Technically - Neo4J is a database, not a solution ... Bloom is a tool on top of the database, also not a solution.

If you want to do clever stuff at "librarian" level - you need to introduce taxonomies, ontologies. If you want to provide a solution, you need to build change management / approvals / etc - even if it is for R&D.