Hi there. Does anybody have experience of placing an EagleFiler library on Proton Drive? If so, any issues or disadvantages? I am busy testing a small library there and it seems fine. Just want to check if anybody has had any issues before I move my whole main library there. Thanks
I’ve not tested it, but there’s some general information about using EagleFiler with cloud storage here. In particular:
-
Only open the library in one copy of EagleFiler at a time. Multiple copies of EagleFiler simultaneously using the same database can damage it.
-
Some of the cloud services do not preserve metadata such as file creation dates, labels, or Finder tags. Lack of support for tags is not a problem for EagleFiler because EagleFiler has its own tag storage and will restore any Finder tags that were lost. If creation dates or labels are important to you, you should choose a service that supports them or use an encrypted library.
I’ve not seen an official spec sheet, but some basic searching suggests that Proton Drive doesn’t support tags or other Mac metadata.
Thanks Michael
I can live with the tag and metadata limitation.
I will let you know how it goes.
I have a half dozen libraries stored in Proton Drive. Dates, metadata, and tags are preserved, and I’ve encountered no problems.
Nice. Thanks for the feedback, Richard.
Me again. I have been doing some testing on Proton Drive. I have noted that Proton changes the date created value to the date that the file was saved to Proton and then feeds this new date back EagleFiler. I rely quite heavily on the date created for sorting. But I am quite determined to move my library to Proton. I would be happy if I could prefix the file name with the date from the date created field in the format YYYY-MM-DD. I see there is a script to append the date. But how do I prefix it in a specific format?
Yeah, that’s what happens with services that don’t support Mac metadata. One option would be to use an encrypted library.
In the script you could change the line:
set _record's basename to _record's basename & " " & _dateString
to:
set _record's basename to _dateString & " " & _record's basename
Here’s a better script that lets you customize the date format:
use AppleScript version "2.4"
use framework "Foundation"
-- Change to false if you want it to append the date at the end
set _prefix to true
-- You can customize the date format as described here:
-- https://unicode-org.github.io/icu/userguide/format_parse/datetime/#datetime-format-syntax
set _dateFormat to "yyyy-MM-dd"
tell application "EagleFiler"
set _formatter to current application's NSDateFormatter's alloc's init
_formatter's setDateFormat:_dateFormat
set _records to selected records of browser window 1
repeat with _record in _records
set _date to _record's creation date
set _dateString to (_formatter's stringFromDate:_date) as Unicode text
if _prefix then
set _record's basename to _dateString & " " & _record's basename
else
set _record's basename to _record's basename & " " & _dateString
end if
end repeat
end tell
Thank you, Michael. You are the best.
Thank you for this script, Michael. It is exactly what I was hoping for. Thanks very very much.