Tags - Renaming, Moving, and Other Issues

Customer question about Display This, renaming and Tags associated with older versions.

"I made Revit Project a central file so that multiple BIM people could update it. I spent a lot of time adding dozens of filters (Display This) to the file. Then someone asked me to rename the container file.  To rename a central file in Revit, you have to open the file detached and save as. I figured this would break the filters associated with the channel and it definitely did. This will cost me two hours of work.  Is there a way to associate or export/import filters from one file to the next? Or, is there a way to safely rename a file without breaking any links to filters?"

The keywords here are allow them to 'Edit' which can change the HASH ID and that the file name changed.  Therefore, AVAIL treats this as new content.  Here are three scenarios I drew up for him.

Great question! Check out the scenarios below.  I bet that SCENARIO 3 matches because where people could update it - it probably saw a new file name along with a new HASH, therefore, it is considered a new piece of content?  Make sense?  If you would have indexed it with the new HASH then updated the file name, then it would have been fine.  Make sense?  If you are going to change the filename in the future.  Makes sure the HASH is updated in the system by re-indexing first before updating the filename.  

SCENARIO 1:  If the file name and/or path changes AND the Hash stays the same, then when you re-index, all the tags will remain because the HASH did not change and a new UUID is created.

CHANGES:

FILENAME ~ Changed

LOCATION ~ Changed

HASH ID ~ Same

RESULTS:

UUID ~ New

METADATA ~ Retain current keys/tags

SCENARIO 2:  If the file name and path remains the same AND the HASH changes, then when you re-index, any new tags will be added to the current tags.

CHANGES:

FILENAME ~ Same

LOCATION ~ Same

HASH ID ~ Changed

RESULTS:

UUID ~ Same

METADATA ~ Adds any new tags and retains current keys/tags

SCENARIO 3:  If either the path or file name changes AND the HASH changes, then when you re-index, a new UUID is created.     

CHANGES:

FILENAME ~Changed

LOCATION ~ Changed

HASH ID ~ Changed

RESULTS:

UUID ~ New

METADATA ~ Current Keys/Tags are not retained unless matches existing HASH

Did this answer your question?