You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With current workflow, if one wishes to move an asset (e.g., an image) into another folder, they have to delete it and reupload it inside another folder. With this approach, blog posts that used the moved image would have to be updated manually to use the moved image, otherwise they show broken image link icon.
An ability to move assets from one folder to another would be a great addition to Burdy as this is a core functionality of any sophisticated Digital Asset Manager.
Points to consider
Burdy maps asset URL to the physical location inside Assets section. If an asset were to be moved, any posts and other places should reflect the change in the URL as to avoid broken links.
Solution in point 1 raises another challenge. Changing links may break access to these assets from external to Burdy resources, therefore a way to provide redirects from the old URL to the new one should be considered.
Alternative solution
Implement something like "Tag folders" which would be virtual, meaning that moving assets between these folders would have no impact on their physical location on disk and their URL. These "tag folders" should also support nesting.
The text was updated successfully, but these errors were encountered:
With current workflow, if one wishes to move an asset (e.g., an image) into another folder, they have to delete it and reupload it inside another folder. With this approach, blog posts that used the moved image would have to be updated manually to use the moved image, otherwise they show broken image link icon.
An ability to move assets from one folder to another would be a great addition to Burdy as this is a core functionality of any sophisticated Digital Asset Manager.
Points to consider
Alternative solution
Implement something like "Tag folders" which would be virtual, meaning that moving assets between these folders would have no impact on their physical location on disk and their URL. These "tag folders" should also support nesting.
The text was updated successfully, but these errors were encountered: