LR Keyword Case

I have a hierarchical keyword structure that contains this
Family
Jason
Jaime
note both start with "Ja" - and the "J" is up-cased.
In the "Click Here to Add Keywords" box I start to type "ja" (note lowercase), for Jason, and the drop down box pops up the 2 above entries as expected. I can click to select Jason or press the right arrow to move ahead in the line and either hit {enter} at this point to post the entry or do a {comma} and add more.
However, I am getting really inconsistent treatment from this. Often it will create a new keyword, "jason" (all lower case) and outside the hierarchy. Then I have to go back and point-click to the real "Jason" and delete the un-wanted "jason" keyword.
Then, for a while, "jason" appears in the drop-down box despite having deleted it from the keyword list. I 'think' this is time-dependent because I don't observe this consistently, either, and I think it disappears after a while.
Occasionally it will get it right (that is posting "Jason" to the photo) - but I haven't found the pattern to do that consistently (from a much longer list of names than in this example).
So, are there some ways around this ?
I have a number of family photos, from a long list of people's names, I am trying to keyword and scrolling up and down the keyword list to point-click is tedious, as well.
The creation of phantom all-lc entries, when you actually select from the drop down is infuriating. Bug or bug-feature ?
jc

I think I may have a partial solution ......Ian's suggestion to clear the list and to turn off "Offer Suggestions from recently entered values" helps. At least this ensures suggestions are pulled ONLY from the current, live keyword list and not from previous typing errors.
What I found - and I think this is why it's so hard to duplicate, is that it is system-speed dependent. It works as expected if I SLOW down and wait for the auto-complete to complete (showing what I typed in black and the auto-complete in blue background), then press the {Enter / Return} key, then add a comma. Pressing the {enter} at the end seems to complete the lookup properly from the real keyword list and then it gets posted.
If I go too fast, then I do start to create these phantom all-lowere-case entries. I then have to remove and correct them before continuing.
Now it's working a lot better.
Thanks, Ian

Similar Messages

Keywords case sensitive when starting with umlaut

I have a keyword in my hierarchy named "Übigau" - a borough of Dresden.
When typing the first letters "üb" in the Ctrl-K keyword field the keyword is not suggested. But if I type "Üb..." it shows up! This is not how it works for every other keyword...
Additionally I noticed the same behaviour for the keyword search/filter field, if I type lowercase, nothing shows up:
If I type uppercase, keywords show up!

This has been acknowledged as a bug by Adobe 1.5 years ago in the official feedback forum; please vote on these topics and add your opinion and details:
http://feedback.photoshop.com/photoshop_family/topics/lightroom_and
http://feedback.photoshop.com/photoshop_family/topics/taking_the_accent_out_of_accents

If CASE Statement can be used just nest to 'WHERE' keyword in sql?

HI All,
There are 2 tables,
dbo.headcount_smart_view & dbo.headcount_user_view,they
are not joined i.e. there is no join between these 2 tables.
User is trying to create the access restriction on table
dbo.headcount_smart_view as below,
The following case clause is just next to 'WHERE' keyword :
CASE select distinct dbo.headcount_user_view.role_cd from
dbo.headcount_user_view where UPPER(dbo.headcount_user_view.cmt_id) = UPPER(@Variable('BOUSER'))
WHEN 8 THEN dbo.headcount_smart_view.l3_id In (select distinct
dbo.headcount_user_view.divid from dbo.headcount_user_view
where UPPER(dbo.headcount_user_view.cmt_id)=UPPER(@Variable('BOUSER')))
WHEN 9 THEN dbo.headcount_smart_view.l4_id In (select distinct
dbo.headcount_user_view.divid from dbo.headcount_user_view
where UPPER(dbo.headcount_user_view.cmt_id)=UPPER(@Variable('BOUSER')))
ELSE
dbo.headcount_smart_view.l2_id In (select distinct
dbo.headcount_user_view.divid from dbo.headcount_user_view
where UPPER(dbo.headcount_user_view.cmt_id)=UPPER(@Variable('BOUSER')))
END
The user is getting 'syntax error', it seems that the value is not getting compared with any column hence getting the error.
can case statment be used just next to 'WHERE' keyword in sql?

I don't have the entire table query...
but could u tell me wil the sql given below work ....
if not, why? and what can be done to make it work ?
SELECT * FROM Customers
where case select CustomerID from customers
when 8 then 'Spock'
when 9 then 'Yedi'
else 'Jedi'
end;
Nope
because of wrong syntax
What the purpose of the case when statement here? I'm not seeing a condition in WHERE. You should use it in a condition like below
SELECT * FROM Customers
where case CustomerID
when 8 then 'Spock'
when 9 then 'Yedi'
else 'Jedi'
end = @SomeParameter
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Keywords are case-sensitive

Does this have any real value?
Being a lousy typist, it causes me a lot of troubles (all recoverable).
Please consider removing keyword case-sensitivity.
Winston Mitchell
Boise, Idaho

"So, that means somebody whose last name is 'Gold' would end up being in the same results for searching for 'gold'?"
Yup, that's the way it is anyway. the Find function is NOT case sensitive.
"You can see where that would be a problem... "
No I can't see how it makes any difference.
Jeff,
The search function is NOT case sensitive. Since it isn't case sensitive, I don't see the need for case sensitivity anyplace. It just cause problems on entry.
Say I have existing keywords:
Birds
Eagles
Bald
Golden
If I enter the keyword "Bald" in the Keywording panel to an image of a Bald Eagle it gets categorized correctly. If I accidentally enter "bald" a new keyword is created at the top of the hierarchy.
If I then enter "bald" or "Bald" in the Find panel all Bald Eagles are found. It also finds "Mt. Baldy". Because of this, I usually just click the keyword "Bald" to find my Bald Eagle images. If I have made a mistake, my search is incomplete.
To correct the mistake, I have to correct the error in the Keywording panel and then delete the bad keyword...not so bad if I notice it right away...which I usually don't. I periodically scan the list for incorrect keywords at the top of the hierarchy.
Winston Mitchell
Boise, Idaho.
LR 1.0, WinXP SP2

Switch case in select statement

I have got the following message, while executing the SQL Query. Appreciate any help pointing what is wrong...
Msg 156, Level 15, State 1, Line 2
Incorrect syntax near the keyword 'CASE'.
SELECT TOP 1 UP.DATAID, UP.START_TIME, datediff(day, UP.START_TIME, getutcdate()) as DayGap
CASE DayGap
   WHEN 0
       THEN 'SAME DAY'
   WHEN > 0
       THEN 'new record'
   ELSE 'other'
END as FinalRe
FROM MTP.USERPROGRESS as UP
where UP.MDATAID = 575 AND UP.LSTATUS = 2
tried the following also, but no luck
SELECT TOP 1 DATAID, START_TIME, datediff(day, START_TIME, getutcdate() as DayGap
SWITCH((datediff(day, START_TIME, getutcdate()) = 0)'ITSZERO', (datediff(day, START_TIME, getutcdate()) > 0)'GT1', TRUE, 'n')
FROM MTP.USERPROGRESS
where MDATAID = 575 AND LSTATUS = 2

SELECT TOP 1 UP.DATAID, UP.START_TIME, datediff(day, UP.START_TIME, getutcdate()) as DayGap,
CASE when DayGap =0
THEN 'SAME DAY'
WHEN DayGap > 0
THEN 'new record'
ELSE 'other'
END as FinalRe
FROM MTP.USERPROGRESS as UP
where UP.MDATAID = 575 AND UP.LSTATUS = 2
-Prashanth

How to disable Automatic UPPER case in SQL Developer

Hi,
I am using SQL developer more than two years. I have recently downloaded SQL Developer 2.1.1.64.
My problem is, while editing the package body when move to newline the previous line get converted to UPPER case automatically. But, I don't want to get all the code I have written to be converted to UPPER case.
I have tried all possible preference changes but no change. Can you please help me how disable the case change in SQL developer.
Looking forward your response.
Thanks,
Prashantha Konkodi

You can always define how you want to format the SQL or normal text by using the keyboard CTRL+' to manage text/keyword case to all UPPERCASE, Initcap, or all lowercase.
The system remembers your settings and will keep the text the same format in future.

How to edit keywords?

My question is: how to consolidate keywords, which by mistake differ by capital (small) letter. For example I have photos with keyword "flowers" and photos with keyword "Flowers". I would like to have all of them with one keyword "flowers".
Unfortunately I cannot change the name in keyword HUD getting message that the keyword already exists. So, what is the simplest and fastest way to make the consolidation?
Thanks.

You can merge identical keywords, but for some reason beyond my grasp they made keywords case sensitive so it won't fix your problem.
The only solution I can think of is inelegant to say the least: Make a smart Album that gathers all the images with the keyword "Flowers" then drag the keyword "flowers" onto all the images in that album. Finally, delete the keyword "Flowers" from your keyword HUD.
You need to make this Smart Album on the library level so you're sure to capture ALL the images with that keyword.
I really hope that someone has a better suggestion.
DLS

Orphaned Case

Can someone explain to me what an orphaned case is in a switch statement. I am not quite sure and I am having a bit of a problem in one of my applications. Thanks!!

Show the code, please.
The keyword "case" only has semantic meaning inside a switch statement. You may have accidently closed your switch statement with a misplaced "}". Delete and retype all of your "}" characters and watch EMACS correspond "}"s with "{"s.

Oracle text search query

Dear Professionals,
I am using oracle text functionality(11g).
Is there any way to replace '-' with space and search the as full text as '18005-12220',or partial(either 18005 or 12220 ) as keyword.
case 1)
select * from search_table where CONTAINS(searchdata,'18005\-12220')>0;
o/p=>18005-12220   xyz abc   address 145
case 2)
select * from search_table where CONTAINS(searchdata,'18005')>0;
o/p=>no rows
case 3)
select * from search_table where CONTAINS(searchdata,'12220')>0;
o/p=>no rows
BEGIN
ctx_ddl.create_preference ('SUBSTRING_PREF', 'BASIC_WORDLIST');
ctx_ddl.set_attribute      ('SUBSTRING_PREF', 'substring_index',   'YES');
ctx_ddl.set_attribute      ('SUBSTRING_PREF', 'prefix_index',      'YES');
ctx_ddl.set_attribute      ('SUBSTRING_PREF', 'prefix_min_length', 1);
ctx_ddl.set_attribute      ('SUBSTRING_PREF', 'prefix_max_length', 10);
ctx_ddl.set_attribute ('SUBSTRING_PREF', 'WILDCARD_MAXTERMS', 10000);
ctx_ddl.create_preference('mylex', 'BASIC_LEXER');
ctx_ddl.set_attribute('mylex', 'printjoins', '_-');
Ctx_Ddl.Set_Attribute ( 'mylex', 'index_themes', 'FALSE');
Ctx_Ddl.Create_Preference('my_text_storage', 'BASIC_STORAGE');
ctx_ddl.set_attribute('my_text_storage','I_TABLE_CLAUSE', 'tablespace users storage (initial 10M next 10M)');
ctx_ddl.set_attribute('my_text_storage', 'K_TABLE_CLAUSE', 'tablespace users storage (initial 10M next 10M)');
ctx_ddl.set_attribute('my_text_storage', 'R_TABLE_CLAUSE', 'tablespace users storage (initial 10M) lob (data) store as (cache)');
ctx_ddl.set_attribute('my_text_storage', 'N_TABLE_CLAUSE', 'tablespace users storage (initial 1M)');
ctx_ddl.set_attribute('my_text_storage', 'I_INDEX_CLAUSE', 'tablespace users storage (initial 1M) compress 2');
ctx_ddl.set_attribute('my_text_storage', 'P_TABLE_CLAUSE', 'tablespace users storage (initial 1M)');
END;

thanks Roger Ford for your valuable suggestion.problem is resolved now.

Non-scripter attempting a metatagging script

my script is doing everything i want except it is converting all spaces and periods to semicolons in the final metatag and i cannot figure out why.
It will be VERY obvious that the attached script is nothing but a bunch of snippets clipped together to perform most of what i want...
I want to run this script at the end as i am completing a project to insert the needed metatags.
i want the project name
i want the copyright info
i want keywords to include all images used in the document
i want to be able to add keywords.
to run this script you will need a character style called    KeywordsCStyle
//-----document title and copyright---------
var myDocument = app.activeDocument;
with (myDocument.metadataPreferences){
    //author = "Adobe";
    copyrightInfoURL = "UPMC.com"
    copyrightNotice = "© 2014 UPMC";
    copyrightStatus = CopyrightStatus.yes;
    //description = "Example of xmp metadata scripting in InDesign CS";
    documentTitle = myDocument.name.split(".indd")[0];
    //jobName = "XMP_Example_2003";
    //var myNewContainer = createContainerItem("http://ns.adobe.com/xap/1.0/", "email");
    //setProperty("http://ns.adobe.com/xap/1.0/", "email/*[1]", "[email protected]");
with (myDocument.metadataPreferences){
        //author = "scott rudy";
        documentTitle = myDocument.name.split(".indd")[0];
//var curDocTitle = app.activeDocument.metadataPreferences.documentTitle;
//var curAuthor = app.activeDocument.metadataPreferences.author;
var curKeywords = app.activeDocument.metadataPreferences.keywords;
Array.prototype.unique = function (){
    var r = new Array();
    o:for(var i = 0, n = this.length; i < n; i++){
        for(var x = 0, y = r.length; x < y; x++){
            if(r[x]==this[i]) continue o;}
        r[r.length] = this[i];}
    return r;
function addXMP(/*find GREP*/findString, /*para style*/paraStyle, /*chr style*/chrStyle, /*insert to*/XMPdest){
// reset search fields
app.findGrepPreferences = NothingEnum.nothing;
app.changeGrepPreferences = NothingEnum.nothing;
// setting search parameters
if(findString)app.findGrepPreferences.findWhat = findString;
if(paraStyle)app.findGrepPreferences.appliedParagraphStyle = paraStyle;
if(chrStyle)app.findGrepPreferences.appliedCharacterStyle = chrStyle;
switch (XMPdest){
    // insert keywords
    case "Keywords":
      var myKeywords = app.activeDocument.findGrep();
      var myKeys = Array();
      // loop through keywords and get contents
      for(var i = 0; i < myKeywords.length; i++)
        myKeys.push(myKeywords[i].contents);
      //myKeys.sort();
      // delete duplicates
      //myKeys = myKeys.unique();
      // insert Keywords to document XMP
      app.activeDocument.metadataPreferences.keywords = myKeys;
      break;
    // Heading search/insert
    case "Heading":
      var myHeading = app.activeDocument.findGrep();
      app.activeDocument.metadataPreferences.documentTitle = myHeading[0].contents;
      break;
    // Author search/insert
   // case "Author":
    // var myAuthor = app.activeDocument.findGrep();
    // app.activeDocument.metadataPreferences.author = myAuthor[0].contents;
   //   break;
// copy all image names //----------------------------------------------//
f = app.activeDocument.textFrames.add({geometricBounds:[0,0,"20mm","20mm"]});
f.contents = app.activeDocument.links.everyItem().name.join("\r");
f.parentStory.texts[0].select();
//-----------change character style-------------------//
var cName = "KeywordsCStyle";
var mCstyle = app.activeDocument.characterStyles.item(cName);
if (mCstyle.isValid)
       app.selection[0].applyCharacterStyle(mCstyle);
app.copy();
// add Keywords
addXMP("\\w{1,}","","KeywordsCStyle","Keywords");
// add Heading
//addXMP("","HeadingPStyle","","Heading");
//add Author
addXMP("","AuthorPStyle","","Author");
//----delete image names textbox--------
f.remove();

I decided to give up on the character style to add keywords so i have to thank JUmp_over for all the help with my complete script...
here it is after i cleaned it up if anybody else has a need to add keywords to their indesign file (and ultimately to the resulting PDFs
//-----document title and copyright---------
var myDocument = app.activeDocument;
with (myDocument.metadataPreferences){
    copyrightInfoURL = "UPMC.com"
    copyrightNotice = "© 2014 UPMC";
    copyrightStatus = CopyrightStatus.yes;
    documentTitle = myDocument.name.split(".indd")[0];
//---------------------add document name-------------------------------
with (myDocument.metadataPreferences){
        documentTitle = myDocument.name.split(".indd")[0];
//-----------------------images to keywords--------------------------//
app.activeDocument.metadataPreferences.keywords = app.activeDocument.links.everyItem().name;
//-------------open file info dialog box---------------------
app.menuActions.itemByID(89092).invoke()

Configure key word shortcuts?

I got pretty excited about moving my photos to Aperture out of iPhoto, and have installed the trial. But as far as I can tell, they've made keywording much harder in Aperture, which will be a deal breaker for me if true.
In iPhoto, I can assign a single-character stroke keyboard shortcut to any keyword, case sensitive for a total of 52 instant keyboard shortcuts.
In Aperture, it appears that the closes thing is the default keyword sets, which have a total of 8(!), that have no mneumonic power at all, being limited to Option-1 through Option-8.
Please tell me I'm missing something. Keywording is such an "I don't really want to take time for this but I know it will pay off" thing that iPhoto's easy, instant application of 52 different ones made it something I was willing to do for the first time. I can't go backwards, which feels especially weird when moving to a pro application.
I have 14,000 images (42 Gb), so I really need to be moving on out of iPhoto to keep growing.
Thanks!
Allen

Keywording in Aperture is more cumbersome than in iPhoto. (I have no idea why.) Nothing you can do with the existing Aperture tools can make keywording in Aperture as frictionless as it is iPhoto.
If that's a deal-breaker, so be it.
Fwiw, I have set up series of custom button sets, mapped controls to a 12-button mouse, mapped controls to the Touch-Ring on a Wacom Intuos4, and tried to integrate voice commands (with Dragon Dictate for the Mac) into Aperture keywording. Each of these helps, but none of them produce as smoothly functioning a system as I had in iPhoto.
I currently use a combination of button sets (rotate through sets with shortcut keys), the Keywords HUD, and the convenient auto-complete of the Keyword entry field on the Control Bar. I am scrupulous about maintaining my Keywords list, have made it hierarchical, and regularly update the button sets. Maintaining a working keywording system in Aperture is laborious. Keywording is -- imho -- perhaps the only glaring weakness in an otherwise facile and up-to-date toolset.

How do I male keywords (only) upper case in a JTextPane

I'm using a DefaultStyledDocument subclass to handle SQL syntax highlighting but what I want to do is ensure that keywords are converted to upper case so as to maintain a "good" style without the hassle of shift or caps lock.
Now, the StyledDocument seems the wrong place to implement this functionality as it should be just for display purposes while changing text to upper case is an actual change to the character values selected by the user.
The JTextPane class itself has a replaceSelection(String content) method but this relies on the text being selected.
I guess I could do this if I had a hook back to the JTextPane from my StyledDocument. When I find a keyword, select the text and replaceSelection.
Is there a cleaner way to do this?

Okay, top tip.
I added the document listener which processed the text on each insert.
At this stage, I've only implemented keyword checking on single character inserts (to capture changes as they are typed) - multi character inserts need to be handled differently.
If I have a character I know can signal the end of a SQL keyword (space, carriage return, brace, parenthesis, comment etc) then I jump back to the last space in the document. This gives me the last "word" in the document.
Remove the last character (as this is the character that has triggered the event) and then see whether it is upper case or not? If not, should it be (is it a keyword)? If so, insert the upper case String in its place.
It was a bit fiddly to put the pieces together (a document listener which then has to use SwingUtilities to make the change using a third Runnable class) but it does exactly what I ask of it.
I have to implement a similar algorithm now to cope with deletions (what if a delete the "a" at the end of "selecta") and multi-character inserts.
Thanks for the advice. I've not used DocumentListeners before so this was doubly helpful.

SQL keywords. lower or upper case?

Hi all!
The plsql parser does any special treatment to sql keywords, e.g, transform all to upper case, before doing internal processing? Same question for SQL scripts/querys!
Thanks,
Rui Rodrigues

Even if there is I'm quite sure any redundant select sysdate/user from dual will outperform all yoctoseconds you'll get.
The other factor for peformance to use some conventions of course is not to flood shared pool with statements that differ just in case and/or spaces for example:
SQL> select user from dual;
USER
SYS
SQL> select USER from dual;
USER
SYS
SQL> SELECT user FROM dual;
USER
SYS
SQL> select SQL_TEXT, SQL_ID, ADDRESS, HASH_VALUE from v$sql
2 where upper(sql_text) = 'SELECT USER FROM DUAL';
SQL_TEXT
SQL_ID ADDRESS HASH_VALUE
select USER from dual
658001za01gf9 68351148 3556818377
SELECT user FROM dual
9rwkva5jwdkfj 6BA2CBE8 1673972177
select user from dual
ahc9t761kxw30 6BAD3E70 2200891488Gints Plivna
http://www.gplivna.eu

Case-insensitive keywords

In my library I have keyworded many pictures with case-sensitive keywords, e.g. "david" and "David". How can I convince Aperture 1.1.2 that these should be treated as if they were identical? (without retyping them manually). If I add "David" to all photos and then try to remove "david" using the shift-return trick, it removes "David", i.e. the wrong one!
iMac G5 21" Mac OS X (10.4.7)

Hi Tim,
the 0.8 stream of Xtext allows to specifiy ignoreCase="true" similar to
backtracking="true" in the workflow that generates your languages. This
should do the trick. Note that this feature is currently considered to
be experimental, but we are working on it to improve its overall usability.
Regards,
Sebastian
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Tim Geisler schrieb:
> What is the preferred way to handle case-insensitive keywords in an
> Xtext grammar?
>
> The special problem in our case is that not all parts of the language
> are case-insensitive, but just some keywords.
>
> Of course content assist is desired also for case-insensitive keywords
> (content assist should then suggest only one alternative for the
> keyword, e.g., with all letters in upper case).
>
> With some experimentation, I found out that from the approaches
> described in the ANTLR Wiki
> (http://www.antlr.org/wiki/pages/viewpage.action?pageId=1782) the first
> approach partially works:
>
> SELECT : ('S'|'s')('E'|'e')('L'|'l')('E'|'e')('C'|'c')('T'|'t') ;
>
> The Xtext-generated lexer/parser then recognizes case-insensitive
> keywords, but there is neither a completion proposal nor lexical
> highlighting of the case-insensitive keyword in the editor.
>
> This can be solved by extending DefaultAntlrTokenToAttributeIdMapper for
> lexical highlighting and extending
> AbstractContentProposalProvider.completeRuleCall().
>
> The not-so-nice issue with this approach are that the lexical structure
> of the case-insensitive tokens is distributed over several classes and
> that enums cannot be used anymore.
>
> Best regards,
>
> Tim

In ALV Report Filter selection should be case sensitive

Dear All,
since one field is case sensitive in database table , i have to fetch that in alv report , but when i am applying filter on that field its is simply fetching data with case description. if its in caps it should fetch caps data but in smaal case report showing no data
Regards,
Pankaj Vashista

Hi,
All text datas are case sensitive.
To make it work perfectly You have to Use the Keyword translate to Upper Case than display
Now filter can work.
Without Transalation to Upper Case filter will not work.
Regards
Arbind

LR Keyword Case

Similar Messages

Maybe you are looking for