When we need to add a new custom listview config or modify an existing one, the entire tdbconfig database needs to be destroyed such that it will re-read the PropertyConfig.n3 file because it's in the firsttime directory.
An example is that we want to create a new config specific for TeacherRoles and Honors/Awards. To do this we also want to modify the config for participant - https://github.com/vivo-project/VIVO/blob/develop/home/src/main/resources/rdf/display/firsttime/PropertyConfig.n3#L1910 such that it won't display to the public. The only way to do this AND preserve our configuration is to rebuild the tdbconfig. We would like to have a couple of improvements to this process.
1. Allow this file to be read everytime and have the tdbconfig database refresh if there are changes.
2. Allow a method to manifest the faux properties to a physical file such that it can be placed in the appropriate VIVO build directory and checked into version control.