On 7/29/21 8:58 PM, nospam wrote:
> In article <sdvqql$at0$
1...@dont-email.me>, Dudley Brooks
> <
dbr...@runforyourlife.org> wrote:
>
>>>> If you would recommend one or several asset managers, I will check them
>>>> out.
>>>
>>> what types of assets do you have?
>>
>> The "assets" that I have are files ... and I want to be able to find
>> them. (See #3, below.)
>
> obviously they're files.
>
> what *types* of files?
>
> photos? music? videos? text documents (pdf, word, etc.)? other?
>
> each type has a different solution.
>
> it sounds like you have text documents, which needs a different asset
> manager than one for photos or videos.
All of the above.
An example: "Wijaya Kusuma" is the name of a music composition by the
Balinese composer I Nyoman Windha. I have .wav files of performances
and rehearsals of the piece. I also have video files of other
rehearsals and performances. I have several Sibelius Music Notation
files of the score of the piece in Western music notation. I have .txt
and .pdf files of notes about the piece, reviews of the piece, and
audience souvenir programs for performances of the piece. I want to be
able to click on "Wijaya Kusuma" in ... something! ... and have them all
show up! Originally they were (mostly) all in a folder called Wijaya
Kusuma. But then I realized that .wav files should probably go in the
My Music folder (or a subfolder) because different info about the file
shows up than if it's in a non-music folder, such as various audio
information. Likewise the various video information shows up only if
the files are in one of the video folders. Not all the files have
"Wijaya Kusuma" in their title ... and some of the files, such as the
programs for the performances, have many other pieces as well, which I
would also like to be able to search for by *their* names.
And the *only* thing I want to be able to do is simply *find* them.
After that, anything else I want to do is handled merely by opening the
files, which of course starts the appropriate program. So I don't know
in what respect they need different "asset management".
>> I'm going to say just a few things ... and then I'm not sure there's any
>> point in continuing this thread. (See #4.)
>>
>> (1) I have so many files that they have become hard to find ... despite
>> having a very well organized file structure.
>
> it's going to be a *substantial* amount of effort to manually keep
> things organized via the file system with even a fraction of the files
> you claim to have.
>
>> (The difficulty there is
>> that, for example, it is hard to come up with a file system structure in
>> which, for example, Information Theory and Common Practice Period
>> Harmony are in folders which are close ... but there is, for example, a
>> paper which applies Information Theory to Common Practice Period
>> Harmony. Hence my original attempt to use Aliases, to get that file to
>> show up in both the Information Theory folder and the Harmony folder.)
>
> that's the problem in a nutshell.
>
> managing files directly in the file system using finder or windows
> explorer is at best, inefficient and worst, a disaster.
>
> creating aliases and moving them into various folders is just begging
> for problems.
I agree.
> asset managers are designed specifically for that task.
When you mentioned asset managers before, I didn't know what an asset
manager was. My first google search turned up elaborate database
management systems and the like, for enterprises. So that seemed like
hitting a fly with a sledgehammer. So now I know what I am looking for.
>
> the computer is there to do work *for* you.
>
>> (2) What I am looking for is something that will let me characterize
>> files according to my own criteria (including multiple criteria per
>> file) and then search for them based on those criteria. So that paper
>> above would have the tags "information theory", "harmony", and
>> (possibly) "common practice period" -- and tags would be especially
>> useful, since those terms might not be in the *name* of the file, so I
>> could search on tags rather than (or in addition to) file names.
>
> by using keywords in an asset manager.
>
> it might be possible to do it with spotlight.
>
>> (3) When I google (or duckduckgo, rather) "what are macos tags for",
>> *everything* that shows up, on the Apple support pages and on user group
>> pages like macrumors, or on individual pages, says some variation on "to
>> make files and folders easier to find". (Some even say "to *organize*
>> [emphasis mine] files and folders" ... but "organize" is ambiguous, so
>> I'll ignore it.) But *yes*, to make them easier to find! (And many of
>> those sites say "by searching on tags".) In other words, *exactly* what
>> I have been trying to use them for!
>
> none of those suggested using thousands of tags.
And none of them said not to use thousands of tags. I'm not sure that
any of them even mentioned numbers of tags at all!
(BTW, I mentioned Firefox only to contrast its ability to apply
thousands of tags *easily* to website vs Finder's inability to do it
easily to files. Yes, Firefox is not a file manager ... but I was not
trying to use tags to *manage* files (whatever exactly that means), only
to find them.)
>> But, evidently, their programming makes them inadequate for this ... at
>> least, at a scale which is truly useful for the large number of files I
>> have, and the large number of categories.
>
> they never intended anyone to use thousands of tags.
>
> it's actually surprising it lets you create anywhere near that many.
>
>> (4) It's not helpful to be told that I should be doing this differently,
>> without be told what I should do instead -- to be told that I am doing
>> it wrong without being told how to do it right.
>
> spotlight
In my use of spotlight so far, it always returned *way* too much -- so
many files that wading through all their names is almost as hard as
simply wading through their names directly in the folders -- and
simultaneously not enough -- i.e. not the particular file I was actually
looking for, it I can't think of the proper search term. But if there
are subtleties (filters? booleans?) to Spotlight, I will try them out --
but I suspect they would have to be used every time you searched, right?
Not something that could be done once (like a tag) and never have to
be done again?
> and/or asset manager.
Yes, I will check out asset managers.
I should mention that, actually, tags work *perfectly* ... once they are
created. Clicking on a tag in the Sidebar or in All Tags *instantly*
populates the list. It's only the *act* of creating a tag which has
become frustratingly slow.
So I do have another question: Whatever it is that an asset manager
does to make it easy to find files, I would still have to set it up,
right? I have already put in a huge amount of time creating those tags
... which *do* work exactly as desired *once* they are created! ... and
wouldn't I have to spend just as much time recreating all *that* work in
an asset manager?
>> (5) So if 3500 is excessive, what number is "appropriate"? In theory, I
>> guess the number of tags (or whatever) needed to *completely*
>> characterize all my files would be somewhere between log-base-2 of the
>> number of files and log-base-2 of the number of bits of information
>> contained in the files -- and that would be *far more* specificity than
>> needed. So I agree, 3500 is excessive. But trying to figure out
>> exactly *which* English-language tags (or whatever) to use is not easy!
>> So, as I acquired new files over the years, and tagged them as seemed
>> appropriate at the time, that's how many I would up with.
>
> in other words, your system is flawed.
Not a useful comment. It's not actionable.
Also, by "my system", do you mean the way I was trying to use tags? If
so, then thank you, you *have* suggested alternatives, which I will look
into.
But if you mean the way I choose to characterize my files and think
about them ... well, then that's just rude. So I will assume that that
is *not* what you mean.
>> BTW, both in my file system and in my use of tags, I started with a
>> small number of folders, and later with a small number of tags. But
>> when the number of files in any of those grew too large, I subdivided
>> ... and then later had to subdivide again ... etc. So the numbers grew
>> exponentially.
>
> yet another reason why using the file system is a bad idea.
>
> the computer is there to do the work *for* you.
Uh ... yes ... that's why I was creating tags on the computer! ;^)
I will definitely look at Asset Managers ... but unless the Asset
Manager is an AI which is automatically going to characterize all my
files for me (ha!), it's still going to have to be *me* deciding on the
classifications or whatever, and telling the Asset Manager how to apply
them to the files ... so ... once I get the Asset Manager up to where it
can do what the tags are already doing, if it will be faster and easier
to use than tags when I acquire *new* files, then that's definitely a
plus. But I'm not looking forward to spending all the time to get it to
that point ... unless there is something I'm completely misunderstanding
that would get it to that point quickly.