[Feature request] Attachments as links to external URLs

[jpbaril]

What is the problem you are trying to solve with this feature?

I use Paperelss-NGX to store receipts/manuals/etc. and so would prefer to keep all my documents in there. Yet, I would want to reference those external documents in Homebox items.

What is the solution you are proposing?

My first thought would be that when adding an "attachment" Homebox would allow to choose between uploading a file to Homebox (as it is right now) or simply link to an external entity/URL.

That way Homebox could continue to reference these external entities as per the usual attachment types (i.e. photos, receipt, warranty, etc.) and so show/use them just like those uploaded to Homebox.

What alternatives have you considered?

I could create each time a custom field for receipts+manuals+etc. and input the external URLs since custom fields allow URL links, but that would not be "clean" and Homebox would not understand "system-wise" what those linked entities are (i.e. receipts/manuals/etc). And having to create a custom field for each file that needs to be linked to is cubersome and can become messy in my opinion.

Additional context

My proposition is really just a general idea / concept, there is maybe a better way to achieve the same goal.

BTW, it's a copy-pasting of a feature request I created on original repo: hay-kot/homebox#704
Also, another user requested the exact same thing a few weeks after: hay-kot/homebox#835

Thank you

Contributions

• I have searched through existing issues and feature requests to see if my idea has already been proposed.
• If this feature is accepted, I would be willing to help implement and maintain this feature.
• If this feature is accepted, I'm willing to sponsor the development of this feature.

[tankerkiller125]

I've converted this into an issue for further discussion and investigation about how this might best be addressed and handled. And for further community feedback.

[kusold]

Homebox's handling of attachments is giving me some hesitation. Currently (0.15.2) stores attachments in /data/${groupUUID}/documents/${attachmentUUID}.${fileExtension}. While using UUIDs for the attachments on the filesystem prevents potential naming collisions, they no longer are human readable. Additionally, attachments aren't included in the export CSV which makes rebuilding a Homebox instance nigh impossible if the database is lost.

The proposed solution of allowing attachments be URLs works well for PDF data. I also run Paperless-NGX and how it handles exporting documents is superb. If #332 adds support for uploading directly to Paperless, that would solve some of my concerns.

There would still need to be a way to Export attachment references so that users can recover from database corruption, or have a way to move their data to a new instance.

Potentially Related Issues:

• Enable attachment export #224
• Filename of attachments is not preserved #288
• [VNEXT] multiple storage provider support #332

[tankerkiller125]

While the filename is not human readable, the original name is stored in the database (although not really used except in the UI at the moment).

Moving data to a new instance is already possible by simply copying the database file to the new location (unless you mean something like importing the data to a different shared instance or something?)

As for corruption, or loss of the db file, properly working backups would resolve that pretty quickly.

[kusold]

I just wanted to come back and say that you were correct that my request doesn't belong in Homebox's code base. Thanks to the API that homebox provides, I was able to implement what I wanted.

https://github.com/kusold/homebox-export

It's pretty basic at the moment, but it currently is able to pull back all of my attachments with their original name. Furthermore, by using the API it should also work with future storage providers. Eventually I might also start exporting the items themselves since the CSV export is a bit limited with the fields it exports.