Current file attachment functionality is based on a 1:M relationship cardinality (a feature can have multiple attachments, but an attached file can only be linked to one feature). In a previous project I had to attach a file to multiple features. This meant storing the file multiple times in the geodatabase (once for each feature the file needed to be attached to), which is an inefficient method of managing attachments in a geodatabase.
An idea for more efficient management of attachments is to have functionality to use M:N cardinality when attaching files to features in a geodatabase. This means:
- A single feature can still have multiple files attached/linked to it.
- A single stored file can be linked to multiple features in a geodatabase.
Managing file attachments in this way would involve a 2-step process. Firstly, the file needs to be uploaded/attached into the geodatabase. Then a second step will be needed to determine which feature(s) the file is attached/linked to.