Fluid Topics v3.7.19 introduces a feature allowing ADMIN and KHUB_ADMIN users to manage map attachments asynchronously (i.e., after the content has been uploaded) in the UI.
Accessing the document in the Reader page and selecting the Attachments tab in the sidebar displays the map attachments interface as follows:
Selecting the button opens the local File Explorer. Uploading a file unfolds a new section where it is possible to modify the display name of the map attachment:
Although is not possible to modify the filename when uploading the file, it is possible to modify it once the file has been attached successfully. This is because the filename is used to build the originId during the initial upload. Changing the filename at a later point will not change the originId.
Fluid Topics automatically detects a media type when uploading a map attachment in the interface. For map attachments added with a control file, Fluid Topics detects a media type during the next update in the interface.
Saving the file adds the map attachment to the document as follows:
At any time, it is possible to expand the section and update the filename or display name or remove the map attachment:
If adding multiple attachments, it is possible to refresh the map attachments interface in order to visualize all files which have been attached successfully.
Be aware that modifications made in the interface to map attachments that were not originally added in the interface can potentially be overwritten in some scenarios:
- For map attachments originally added synchronously, reuploading the map attachments synchronously in the future overwrites the configuration in the interface.
- For map attachments originally added asynchronously with a control file, reuploading the map attachment synchronously in the future does not overwrite the configuration in the interface.
- In all cases, uploading the original map attachment with a control file overwrites the configuration in the interface.
If the same file with the same name is attached to different publications via the interface, it will not be the same entity in Fluid Topics.