Query Based Classification & custom properties

Hi all,
Is there a way to build a query based classification with custom properties?
Regards,
Orlando Covault

Hi Frank,
Very cool documentation, Ill give you points for that but my question remains and I think that the answer is no... Theres no way that I could use custom properties in the Query base classification I am waiting for my environment to run some test, but if some one have another comment on this subject Ill appreciated it.
Regards,
Orlando Covault
P.D. I have another question about the taxonomies and is about changes in the taxonomy, What happens if some moment I need to change a Taxonomy, is this supported and completed functional? I mean the classification remains and work fine or is not recommended?

Similar Messages

Tip on Using "Folder" for performing Query Based Classification

In setting up a TREX taxonomy for one of our intranet sites we concluded that the folder structure used by the web developers really helped classify the documents at a higher than an 80% level. It seems that in many cases, the intranet, outlook public folders, or LAN folders will be organized such that the title of the folder is very valuable in classifying what is in it.
After many searches and false starts, I found something that is so simple and elegant, I had to share it here.
In the Taxonomy Query Builder there is a property "Folder". Unlike the property "Content" which has a "contains" operator, this one is a "Is" or "Is Not" so it seemed like it might be hard to use.
What I found is that it automatically put an * at the end of whatever we entered and if we put an * in the beginning, it seemed to find the folder consistently.
So for a three level taxonomy such as:
-- Business
Customer Support
   Product information
where you have folders /Business/CustSupport/ProdInfo you use a three level taxonomy.
For the business I put in a Query:
-- Folder is_not PassTheIsNotTestSoEverythingIsClassified
That meant everything was included at the root level no matter what. (i.e. I didn't want 'documents to be classified' to contain anything.)
The query for the Customer Support level of the taxonomy was:
   -- Folder is *CustSupport
which pulls in any document that is in the folder that contains CustSupport
The query for the next level was:
   -- Folder is *ProdInfo
which pulls in any document that is in the folder that contains ProdInfo
As the classification engine works, items that pass all three test are put in the most detailed folder. You can have as many taxonomy nodes at any level as you need and if they don't pass any, they are kept at the root of last level they did pass.
You end up with an amazingly simple classification scheme that can handle a big taxonomy. To the extent your folders are not organized like your taxonomy or are not related logically, they you need to add in other queries using the document contents, or other fields available for indexing.   This is where the 80-20 rule kicks in, you still need to work hard to get that last 20%.
Let me know if this approach helps anyone.

HI
r u trying to define properties at the document level then it doesnot works because metadata of KM and metadata of document are different.
u can define pre-defined properties at the folder level in KM.
why dont you use example based classification as u train ur taxonomies with example and it inturn index furher document automatically based on your example document.
But it still deponds upon individual requirements.
Regards,
Vijay.

Query Based Classification Issue

Hi all,
I have got a scenario where I have to classify some project related documents based on the Project Name, Document Type, Module etc. I believe the best way to do this is using Query Based Taxonomies.
But, If I dont have a naming template for the documents and cant assign predefined propertied to documents, what is the best alternative to get the classification done?
Thanks and Regards,
Ajay.

HI
r u trying to define properties at the document level then it doesnot works because metadata of KM and metadata of document are different.
u can define pre-defined properties at the folder level in KM.
why dont you use example based classification as u train ur taxonomies with example and it inturn index furher document automatically based on your example document.
But it still deponds upon individual requirements.
Regards,
Vijay.

What is the use of custom properties for terms in term store management of SharePoint 2013

Hi All,
Can some one pls explain what is the purpose of custom properties for terms in term store management tool of SharePoint 2013.
In general, for each term we have shared and local properties. What is the real purpose in terms of SharePoint development.
Please share with possible scenarios. Does it refer's to a hierarchical metadata in SharePoint ?
Thanks keshav,Share point Developer

The custom properties for terms allow you to further define or clarify a term via the properties. You can then display these properties in search results or specify query rules that look for specific custom properties.
Here is an example of how to create a query rule using custom properties:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/a8b53ffe-869e-4c86-8c43-d239370ee7d5/custom-properties-of-the-managed-metadata-service?forum=sharepointgeneral
Here is an example that uses code to verify that a custom property exists on a term object that is pinned to another term object:
http://msdn.microsoft.com/en-us/library/jj163273.aspx#SP15_H2UseCodeToPinTerms_CodeVerifyCustomProperty
Doug Hemminger http://www.sharepointdoug.com

Report based on custom Query - Question about Data Source

Hello,
I am trying to create Crystal reports (EBO R3.1, Oracle 11g Database, CR2008) based on custom queries. Tried using different kinds of Data Sources but getting stuck once I export them to Infoview.
1. Using Oracle Server: This method works fine on my local & Infoview. But since I have lot of reports, I do not want the DB username/password associated to the report. I neither want BO to prompt username/pwd to my user.
2. Using ODBC(RDO):
Again, works fine on my local. Once I export to Infoview, it fails with this error: "Failed to open the connection"
Which makes sense, because the DSN is created on my local machine and not on the server.
How and what do I create on the server, so that the reports run?
I do not know if using ODBC(RDO) is even the right way for creating custom SQL reports.
I have been reading about Business Views, but not clear on how good they work.
My goal is to create multiple reports, using custom SQL queries which use some kind of connection to the database that can be managed on the
server in one place, and used by multiple reports.
Can any of you please help me here
Thanks,
Sowmya.
Edited by: SBat22 on Apr 13, 2011 5:58 PM

Thanks for moving it to the right forum!!
But, if I setup in CMC, a default username/password that the report needs....what would happen if my password changes?
I would need to go to each and every report and update the password.
I am looking for using one common "connection" for multiple reports. So that, when passwords change, all I update is in one central location.
Can anyone please help!
Thanks,
Sowmya.

Custom Corporate Directory Query Based on Department

I need to limit specific queries from Corporate Directory search based on Department. CCM 4.1(3)
My Goal is to create separate directory options, each associated with a specific department (I've done this) and then limit the query to ONLY users in that department (I need help here. :-|
The Flow as Joe sees it ~
User selects directory button.
(Based on info from xmldirectory.asp...)
User is provided with the following menu:
1. Missed Calls
2. Placed Calls
3. Received Calls
4. Department A
5. Department B
6. Department C
(I've got this far by adding new menu items to the xmldirectory.asp file, and then I tie those to separate xmldirectoryinput.asp files, which I plan to use to limit the query based on dept)
<MenuItem>
<Name><% = outputString( "Department A", "dictionary.lblCorporateDirectory" ) %></Name>
<URL><% = getBaseURL() %>A_xmldirectoryinput.asp</URL>
</MenuItem>
<MenuItem>
<Name><% = outputString( "Department B", "dictionary.lblCorporateDirectory" ) %></Name>
<URL><% = getBaseURL() %>B_xmldirectoryinput.asp</URL>
</MenuItem>
<MenuItem>
<Name><% = outputString( "Department C", "dictionary.lblCorporateDirectory" ) %></Name>
<URL><% = getBaseURL() %>C_xmldirectoryinput.asp</URL>
</MenuItem>
Next when the user selects 4. Department A, they should receive the standard
First Name:
Last Name:
Number:
However, When the user selects "search", I ONLY want them to see directory entries in Department A, and not the entire Corporate Directory. So I need A_xmldirectoryinput.asp to limit the query to Department A. Actually ~ I've just added the Department menu item via the xmpldirectoryinput.asp file, and prepopulated it with the Deparment of my choice, though now, I'm stuck on the xmldirectorylist.asp, and how to Query for the DepartmentNumber ... Help please??? :)
If they select Department B, ONLY Department B, etc.
What do I need to add to, or reference in the xmldirectoryinput.asp to restrict the search to a specific department?
Also - Would any changes, additions, etc. be required in the xmldirectorylist.asp file?
THANKS IN ADVANCE!!!!! :)
Joe

Please use IDM forum for IDM related questions. This is proxy forum.

Documents in Query-based Taxonomy are not Autoindexing

Hello experts!
I am on EP6.14 with Trex 6. I have a repository with a query-based taxonomy on it and is also part of a regular search index. I have autoclassification on.
On each document I have a couple of properties that are used to match documents in queries in my taxonomy. On the initial set-up and load, everything worked great. Documents went right where they were supposed to. But sometime after we released this to the business, the documents no longer automatically index. If I change a document property or set up a new one, it finds the category but leaves them as "suggested." You then have to go in and accept those suggestions to get the document to the right taxonomy. In short, it acts as if autoclassification is off. I have noticed that the Classification index does not submit a new document if I change a property but the search index does. Not sure if that is applicable but I would think both should do that since it is a change.
I did some research and found that synchronization issues or new folders could cause this problem but I have synchronized with no success. Also, state management is not on for the repository.
Is there any reason why autoclassification would stop on its own? What can I do to get it back on?
Thanks-
J
Many points given for helpful answers!

Hi Frederick-
Thanks for your response-
We have a single CM DB repository. There is a search only index at the root folder and classification index on a folder below the root. Normally, we don't overlap but we wanted only the folders in the lower folder to be part of the taxonomy. I suppose we could just rule out the other documents by not having them match any queries but this way it was guaranteed.
THe search and classifications are working (aren't throwing errors) but like I said, I would think that both would have to push the document through the queue. But I'm only seeing the search index do that. Now if I go and accept the recommended categories, then it goes into the queue for the Classification index.
J

Filter a Query Based on the Output of Another Query

Is it possible to run a query based on the put put of another query? I have two queries. One query is based on GL Line items and shows the account assignemnt of postings where a customer has had a debt raised and it been credited to an account assignment e.g. Order, Cost Centre or Profit Centre. The other query is on an AR cube and that shows payment made. I want to bring these together to show the owners of the various account assignments to what extent customers have actually paid the debts that have been raised and credited to them. This I do as the source document of the CO doscument matches the allocation of the ar document. So I have a query that shows the CO journal and another query that shows payments. But I only want to show the payments in the second query for documents displayed in the first query (which can be restricted by period and fiscal year and the particular account assignment).

Hi,
This can be acheived by usign a replacement path variable.
Create replacement pathe variables for those the filter values in the second report nneds tobe restricted from the first.
Then in the properties of the varioable say replce by query result and input the first query name in it.
Use these variables in teh filter section of the second report.
Make sure the characteristics for which you created the replacement path variables are in teh row section of the first Query.
Now on executing the second query you will have it filtered based on teh values of the first Query.
Hope this helps.
Regards.
Shafi.

Query Based Taxonomy and Searching Problem!

Hi all,
Ive an urgent problem to solve ....
I create some customs properties with dependent values, for example, if I put Country: Germany, I ve three options, (Waldorf,Munchen,Berlin) and so on ...
Then, I create a Query Based Taxonomy, where in some categories Ive a query, with the dependent value (Ex: Waldorf) ... I mean, If City = Waldorf, the document belongs to this category.
So, when I do this, the taxonomy fails ... Only with the dependent value, I mean, if the category is with the base property (Ex, Country) it works.
Plese, help!
Cheers,
Andres.

Hi,
To include a dependant property in a query, you have to enter both parent (Country = Germany) and the dependant (City = Munich) properties in the category.
Hope this help
Kind regards
Vincent

Query based taxonomy from scratch gives NoSuchMethodError...

I'm trying to create a query based taxonomy following the instuctions specified in the help docs: KM Platform -> Admin Guide -> Content Mgmt -> Taxonomies and Classification -> Creating a QBT -> from scratch. I created an index on a newly created (hence empty) folder in the 'documents' repository. So, essentially, the data source points to that folder. Also, I selected 'TREX Classification' on the 'Service' drop-down while creating the index. I left the crwler profile as blank. Then I went on to create a new 'Query Based Taxonomy'. I was able to create it alright, but as soon as I click on it to add folder and the such, I get this error:
java.lang.NoSuchMethodError
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.getDocumentTaxRMRids(TaxonomyNamespaceManager.java:1876)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.getTaxonomyClassResources(TaxonomyNamespaceManager.java:1831)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.addChildDocuments(TaxonomyNamespaceManager.java:1942)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.getChildren(TaxonomyNamespaceManager.java:368)
     at com.sapportals.wcm.repository.CollectionImpl.internalGetChildren(CollectionImpl.java:966)
     at com.sapportals.wcm.repository.CollectionImpl.getChildren(CollectionImpl.java:179)
Any help in solving this is highly apprecaited.
We run EP6 SP2.
I did NOT create a 'crawler profile' for this set up.
thanks,
Biju.

Hi Biju,
re. your NW'04 SP stack 4 migration intention:
NW'04 is still in ramp-up (SP stack 4 is the current shipment bundle of it) so at the current point in time, only participating ramp-up customers can use it.
A migration from EP6.0 SP2 to NW'04 will be possible (but not during the ramp-up phase).
From a Knowledge Management & Collaboration perspective, we will port most of the NW'04 SP stack 4 functions to EP6.0 SP2 as well. These functions will be shipped as EP6.0 SP2 Patch 5 (planned shipment date beginning of Q4 / 2004) so for mid-term, you can also plan to stay on EP6.0 SP2 if you have no other pressing reasons for going to NW'04 (e.g. enhanced Web AS functions).
This feature porting from NW -> EP6.0 SP2 is an 'only-once' action, however, and NetWeaver will be the release for new features in the future.
Regards,
Joerg

Query Based Taxonomy - Dynamic Creation of a Query Problem

Hi,
I'm trying to create new category nodes in a taxonomy and to assing them queries. I know how to do this, but I encountered a strange behavior. Here is the situation:
I have a string property DocumentType. When manualy creating a query, it looks like:
DocumentType CONTAINS "Some string"
But when I do the same using code I get:
DocumentType IS "Some string"
And as a result of this, the taxanomy is not working properly.
Here is the code:
     indexService =
     (IIndexService) ResourceFactory
     .getInstance()
     .getServiceFactory()
     .getService(
     IServiceTypesConst.INDEX_SERVICE);
     //        This kind of classification index offers functionality working with query based taxonomies
     qbcIndex = (IQBClassificationIndex) indexService.getIndex(indexId);
     //        Get a query folder - a query folder is a representation of a query based taxonomies category
     queryFolder = qbcIndex.getQueryFolder(RID.getRID(folder));
     //        List of IQueryEntry objects for the query folder
     queryEntryList = queryFolder.getQuery(context);
     //        Cast the IQBClassificationIndex into a ISearchIndex object
     searchIndex = (ISearchIndex) qbcIndex;
     queryEntry = searchIndex.getNewQueryEntry();
     queryEntry.setRowType(IQueryEntry.ROW_TYPE_ATTRIBUTE);
     queryEntry.setPropertyName(propertyName);
     queryEntry.setPropertyOperator(IQueryEntry.PROPERTY_OPERATOR_EQUAL);
     queryEntry.setValue(propertyValue);
     queryEntry.setTermAction(IQueryEntry.TERM_ACTION_EXACT);
     queryEntryList.add(queryEntry);
     //        Set the query for the query folder
     queryFolder.setQuery(queryEntryList, context);
     qbcIndex.updateCategoryContents("Document_Types", false, context);
Can somebody tell me what am I doing wrong please. Isn't it because of IQueryEntry.PROPERTY_OPERATOR_EQUAL? Is there any substring operator?
Thanks a lot.

Hi, Robert
In this moment, I have a problem with Query Based Taxonomy, maybe could you help me. I insert the query in to the taxonomy from code, but when i use the method
qbcIndex.updateCategoryContents("/taxonomies/borrame5/Prueba2", false, context);
I got the next exception:
#1.5#0014C210F3D1002A000001200000565B000431CC93AD5979#1180654627543#System.err#sap.com/irj#System.err#dummy01#10241#####SAPEngine_Application_Thread[impl:3]_17##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
#1.5#0014C210F3D100310000012B0000565B000431CCC47166AB#1180655445698#System.err#sap.com/irj#System.err#dummy01#10241#####SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Plain###com.sapportals.wcm.service.indexmanagement.IndexNotReadyException: Some documents are not included in this update because indexing has not been finished yet.#
#1.5#0014C210F3D100310000012C0000565B000431CCC4717417#1180655445701#System.err#sap.com/irj#System.err#dummy01#10241#####SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Plain###     at com.sapportals.wcm.service.indexmanagement.retrieval.trex.AbstractTrexIndex.updateCategoryContents(AbstractTrexIndex.java:2493)#
I have doubt what parameters i need to pass to the method updateCategoryContents,
Let me give some information:
taxonomy:
   /taxonomies/borrame5/Prueba2
repository:
   /documents/Portal_KOF/KM/Pruebas1/Pruebas Versionamiento
classification and search index:
   borrame5
   I can't classify automatically, when i insert the query from code. When I manually insert the query from the portal, automatic classification run perfectly.
Thanks
Greetings
JARO.

Query based collections SCCM 2012 R2

Hi to everyone. Is there any book or other material needed to master process of creating query-based collections? It is done using WQL not T-SQL so it is a little bit tricky, not only syntax itself but also classes where particular information useful to
create custom query-based collection can be found. I used WQL before only to create WMI filters for some GPOs in order to narrow their scope e.g. only to Windows 7 workstations in domain. These WMI filters were usually created
with one short WQL line, it was very simple WQL query. Bare in mind all classes that exist in SCCM database googling can be useful to solve some problems but it would be better to have some book and to master creation of query-based
collections.

Hi,
You could review the file smsprov.log.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Combo box in "Filter by Custom Properties"

Hi to all,
I create some custom metadata properties properties in order to classifie the documents in KM.
This metadata properties has a set of Allowed Values, so the value is selectable with a combo-box in Detail box of KM.
Now I have to enable the Filter by Custom Properties with the combobox in place of textfields.
How to do?
Regards,
Giampaolo

What you want is not the Filter by Custom Properties but the Filter by Predefined Properties.
In you search options configuration add your properties to the predefined properties list and you'll get your combo-box.
To configure your search options go to:
System Administration -> System Configuration -> Knowledge Management -> Content Management -> User Interface -> Search -> Search Options Set

Disc 4137 - query based on login?

We have a sales table in Discoverer that we want to allow sales managers to access so they can define their own ad-hoc queries. However we only want them to be able to query based on sales attributed to them i.e. they can't query on other sales managers.
I know I can build business areas for each sales manager and create a custom folder in each area with the sales manager pre-defined to limit queries but to simplify the maintenance I'd like to be able to limit the queries based on how the user logs into Discoverer. i.e. username 'ABC' logs in; view has logic to recognize 'ABC' as the username and automatically sets a condition to sales_manager='ABC'.
Is something like this doable with Discoverer? I know we can get the username via forms but didn't know if Discoverer offered this functionality too.

Actually, what's been said is correct for database EULs.
However, for Apps-EULs, it is possible to determine the Oracle Apps user and/or the Oracle Apps responsibility that's presently logged in to Discoverer (requires an external routine to be registered but it's an Oracle one).
Then, if an Apps-EUL, you can limit the folder in the EUL to that responsibility, etc. in the same fashion as stated for the DB-EUL.
Note that some of the views in the database may indeed only show info for a particular apps user / responsibility, but these views are usually only the BIS views and if you look at the code to these views, it's obvious as one of the last lines will refer to a package such as: HR_Security_Pkg or GL_Security_Pkg.
However, if you're going straight to an Oracle table and it's an Apps-EUL, then what I mentions works - done it many times now.

How to add a selection criterion to a SQ01 query based on logical database SDF?

Hi,
How should I add a selection criterion to a SQ01 query based on the logical database SDF? Is it possible through additional code? How to make use of the custom selection fields? I need a selection criterion based on BKPF-CPUDT (creation date).
Thanks.

Hi John,
Please check the given below link in addtion to Atul post.
http://scn.sap.com/community/erp/sd/blog/2012/04/16/query-report-tips-part-2--mandatory-selection-field
Thanks,
Senthil Maruthappan.

Query Based Classification & custom properties

Similar Messages

Maybe you are looking for