Methods for re-pathing Harvested and non-Harvested content
In the three scenarios listed below, AVAIL provides automated file re-pathing in scenario 1 (with Harvest) and scenario 3. For re-pathing of non-Harvested content (scenario 2), to fix broken links, we have a document with best practice steps that make re-pathing easy while retaining your content tags.
- Using AVAIL Harvest to re-path harvested content
- Re-pathing non-Harvested content
- Bulk re-pathing of content when file systems change
1. Using AVAIL Harvest to re-path harvested content
As AVAIL Harvest brings visibility to elements (like drafting views, sheets, view templates, materials, and more) in Revit container files, the resulting accessible content is managed by AVAIL's database. The database tracks relevant content management data including tags, thumbnails, previews, network path to content source, related content links, ID of the Revit container files from which Harvest is run, and other functional data.
When performing search, preview, load, place and other functions with AVAIL, correct access to the AVAIL database is needed. Manually moving Harvested content to different network locations, and/or re-indexing Harvested content, breaks some of the connection points to the database and undermines AVAIL functionality.
AVAIL recommends:
- Do not manually move harvested content to different network locations.
- Do not re-index Harvested content.
Let Harvest re-path to a different network location for you instead
The steps are:
- Harvest Revit elements (drafting views, groups, schedules, legends, view templates, etc.) from a Revit container file. In the Harvest settings, set the AVAIL Channel to publish to, and the network destination for storing the harvested content.
Later, when you determine the network storage location must be moved, do the following steps:
- Open Harvest again from the same Revit container file, and change the Harvest setting that specifies the path to the network storage location. Change it to the desired new location.
- Run Harvest
- Harvest handles the re-pathing for you. The content is harvested to the new location on your network, and the published content in your AVAIL channel is automatically re-set to the new target path on your network. All tags present on the content are retained after the re-path.
Important Tip: Harvested content should never be Streamed and should never be moved, or indexed, manually. Use Harvest instead to do this.
If previously harvested content is re-harvested, by Harvest, to the same Channel but to a new network location, the Harvested content that was previously published to an AVAIL Channel will be automatically re-pathed to point to the new network location.
If previously harvested content is re-harvested, by Harvest, to a new Channel and a new network location, this will not create a second piece of content. The content will remain in the original channel, will be re-pathed to the new network location, and if a new channel is selected, the content will also be added to the new channel.
In AVAIL, harvested content can be added and removed from channels, as desired.
But what about non-Harvested content that gets moved to different locations on the network? That's scenario 2:
2. Re-pathing non-Harvested content
The steps in the document here https://helpcenter.getavail.com/how-to-fix-broken-content-paths are the easiest way to restore links, and retain tags while avoiding possible errors when non-harvested content gets moved to a different network folder and an AVAIL Channel becomes disconnected from its source location (broken link).
3. Bulk re-pathing of content when network folder structure changes
In cases where your network folder structure is planned to undergo major change, contact AVAIL. We can help you implement bulk re-pathing of content.