Should spaces and/or commas be avoided in keywords?
Should spaces and/or commas be avoided in keywords?
Is there any reason avoid commas and/or spaces in key words that are embedded in images? For example, would "LastName, Firstname MiddleName" be better as LastName_Firstname_Middlename?
Re: Should spaces and/or commas be avoided in keywords?
In general you shouldn't have to edit keywords directly when using Photo Supreme.
Create Catalog Labels instead. There's no need to avoid spaces or commas in catalog label names. On syncing, the catalog labels become keywords in the metadata
Create Catalog Labels instead. There's no need to avoid spaces or commas in catalog label names. On syncing, the catalog labels become keywords in the metadata
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: Should spaces and/or commas be avoided in keywords?
Thanks Hert. I should have been more specific with my question. I was aware that catalog labels are the way to create keywords in PS, and that PS searches work fine with spaces and commas included. My question concerns whether other popular applications are also fine with spaces and commas in keywords. My worry stems from the fact that not all operating systems tolerate spaces in filenames.
Also, for the benefit of other novices like me, I will note something I learned very recently: Catalog labels become keywords only if the correct options are selected in the "details of the catalog label." Specifically, under "Metadata settings", the option "Create keyword for this label" must be selected and I believe you also must select option "Mapped to" dc:subject. I learned this when a catalog label failed to show up in keywords. Not sure how the correct options were not set by default, as they must have been for earlier labels I created.
Hert, please correct me if I've disseminated any false information.
Also, for the benefit of other novices like me, I will note something I learned very recently: Catalog labels become keywords only if the correct options are selected in the "details of the catalog label." Specifically, under "Metadata settings", the option "Create keyword for this label" must be selected and I believe you also must select option "Mapped to" dc:subject. I learned this when a catalog label failed to show up in keywords. Not sure how the correct options were not set by default, as they must have been for earlier labels I created.
Hert, please correct me if I've disseminated any false information.
Re: Should spaces and/or commas be avoided in keywords?
When you create a catalog label then leave all the options as default. Just name it and you're done. Change other details only when needed. "Create keyword for this label" is the default for a new catalog label. Change this only if you don't want a keyword created for a catalog label (the catalog label then becomes private).
This is not needed.Mapped to" dc:subject
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
-
- Posts: 108
- Joined: 09 Oct 08 1:22
Re: Should spaces and/or commas be avoided in keywords?
While catalog labels handle commas fine, other applications may not.
I export my photos and ingest them into Synology's Photo Station. My names are Last Name, First Name. Photo Station split these into individual tags.
So now my catalog labels are Last Name; First Name. (semi colon)
I export my photos and ingest them into Synology's Photo Station. My names are Last Name, First Name. Photo Station split these into individual tags.
So now my catalog labels are Last Name; First Name. (semi colon)
-
- Posts: 219
- Joined: 15 Jun 10 23:36
Re: Should spaces and/or commas be avoided in keywords?
I use hyphens instead of spaces in all multi-word catalogue labels. It works far better when searching, for me.
Re: Should spaces and/or commas be avoided in keywords?
For the search bar, that doesn't matter. Space and hyphen are both word separators leading to the exact same search results.It works far better when searching, for me.
But a hyphen is the character that is used for NOT operations, which should complicate searching.
For instance;
Consider a catalog label named John Doe. You say that you would create that as John-Doe
Using the search bar, when entering
john-doe
This means john and NOT doe. So you you'd have to enter double quotes instead "john-doe" to get the expected result.
Personally I would say that John Doe plays better than John-Doe
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
-
- Posts: 219
- Joined: 15 Jun 10 23:36
Re: Should spaces and/or commas be avoided in keywords?
I don't use not, and for what ever reason, searching for labels containing hyphens works better than labels containing spaces for me.
Re: Should spaces and/or commas be avoided in keywords?
Spaces correspond to an "or" search. Hyphens to a "not" search. Personally I make all my label single words, if necessary with internal capitalisation, or I use an underscore "_" as a space equivalent. So JohnDoe or John_Doe. Seems to work for me.
Jim (Photo Supreme: AMD Quad-Core A8-5500 Accelerated Processor 3.2 GHz; SSD; 16GB DDR3 SDRAM; Win10x64)
Re: Should spaces and/or commas be avoided in keywords?
Unless, like LifeIsLong, you also use software that doesn’t handle spaces correctly there should be no need to cripple the names of your catalog labels.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
-
- Posts: 219
- Joined: 15 Jun 10 23:36
Re: Should spaces and/or commas be avoided in keywords?
An underscore is probably a better choice in hindsight.
Re: Should spaces and/or commas be avoided in keywords?
But I don't find them crippled, just clear, precise and trouble free, as, I suppose are %FileName and %ImageNumberHert wrote: 06 Sep 19 5:09 Unless, like LifeIsLong, you also use software that doesn’t handle spaces correctly there should be no need to cripple the names of your catalog labels.
Jim (Photo Supreme: AMD Quad-Core A8-5500 Accelerated Processor 3.2 GHz; SSD; 16GB DDR3 SDRAM; Win10x64)