Returns information about schema-scoped objects in the current database. For a list of schema-scoped objects, see sys.objects (Transact-SQL). This function cannot be used for objects that are not schema-scoped, such as data definition language (DDL) triggers and event notifications.
SQL Server MetaData Functions July 9, 2013
Managed Metadata MultiValues and Indexed Column June 1, 2012
Update Enterprise Keywords Using Remote API May 1, 2012
You can use the above approach with the client object model.
SharePoint Metadata DialogView and Internet Cache April 23, 2012
So let’s take a look at the HTTP call and the data returned. The call to owssvr.dll looks like this.
GET /somesite/_vti_bin/owssvr.dll?location=My%20Committee/Agenda%20attachment%20July%2009.doc&dialogview=SaveForm HTTP/1.1
When you think about it, there can be many potential causes here. Given that Internet Explorer is effectively doing the work (WinINet), this whole process could be adversely affected by add-ins, zone settings, AD policies, virus scanning, etc. On one affected PC I disabled all all-ins to Internet Explorer and retried without success. After around half an hour of frustration, I decided to reset IE’s configuration as shown below.
MetaData Navigation December 17, 2011
Namespace: Microsoft.Office.Server.WebControls Assembly: Microsoft.Office.DocumentManagement (in Microsoft.Office.DocumentManagement.dll)
Namespace: Microsoft.SharePoint.Taxonomy.WebServices Assembly: Microsoft.SharePoint.Taxonomy (in Microsoft.SharePoint.Taxonomy.dll)
Wrong documentation for the newTerm XML packet.
Problem with Adding a term.
Your code need a bit modification. You need to call termStoreTerm.CommitAll(); after “termSet.IsOpenForTermCreation = true;”. When you change the value of IsOpenForTermCreation, there’s a commit pending. So if you try to add a new term and then commit then the conflict comes up. Your code will look like below after the modification:
SPSite siteTerm = new SPSite(siteURL); TaxonomySession sessionTerm = new TaxonomySession(siteTerm); TermStore termStoreTerm = sessionTerm.DefaultSiteCollectionTermStore; TermSet termSet = termStoreTerm.GetTermSet(TermSetID); termSet.IsOpenForTermCreation = true; termStoreTerm.CommitAll(); termSet.CreateTerm(Term, sessionTerm.TermStores.DefaultLanguage); termStoreTerm.CommitAll();
However you can check if IsOpenForTermCreation is true. If so you don’t need to modify the value and commit.
Programmatically Add Term to Term Set July 25, 2011
$termSet = $termStoreGroup.CreateTermSet(“Term Set Name”)
#Create term, term description, and a synonym
$term = $termSet.CreateTerm(“Test Term”, 1033)
$term.SetDescription(“This is a test”, 1033)
$term.CreateLabel(“This is a test synonym”, 1033, $false)
#Update the Term Store
XML driven metadata update with GUID in input file.
Good tips on the metadata service. Including SQL to get terms and GUIDS for the terms.
MSDN developer introduction.
MSDN Taxonomy API
Local Term Store July 21, 2011
So far, so good – so why am I even writing about this? Well, the biggest problem
is that using a local term store means the site collection cannot be easily
backed up and restored – even to the same farm! So, if I were to take a backup
of my site collection, delete it, and then restore it from backup, this would
severe its connection with the term store group, the currently assigned values
would get ‘orphaned’ (i.e. greyed out and unchangeable), and the next time I
would try and access the properties of my ‘Document Class’ column, I would get a
Metadata Service Tips March 30, 2011
Frontpage Extensions and Sharepoint and Metadata September 22, 2010
The rpc frontpage call “put document” will not work with the new open document standard (xps) in office 2007 files. The code in the author.dll fails to find the properties when they are stored in the xps/xml format. You may want to test this using SP1 to see if it is fixed. The work around when working with xps type files such as docx is to use the “put document” and then do another rpc call “setDocsMetaDataInfo” setting the properties explicitly. The other problem with the Doc files is a property demotion issue. You may want to read the link below about document parsing with property promotion and demotion to make sure all things are aligned for this to work.
After uploading a file you can examine the metadata that is generated for the document in the “AllDocs” table in the corresponding content database in sql server. Below is an example of what is generated in the metaInfo column of the table when you upload a file.
vti_error0:SX|Could not process the file mosstestsearch/test.doc as a Microsoft Office document.
vti_cachedcustomprops:VX|Subject Keywords _Author _Category _Comments
You can see when uploading Office 2003 files SharePoint adds a metadata error entry “vti_error0″ stating “Could not process the file as a Microsoft Office document”. Hmmm. I do believe this is an office document, just not an Office 2007 document. The document’s properties are promoted correctly because I can go into the SharePoint UI and view the properties. For instance, vti_title maps to the title property and testcol maps to the testcol property. Unfortunately, if I open this document in Office 2007 none of the properties are visible. So why are these properties not getting demoted correctly? The key here seems to lie with the “vti_cachedcustomprops” property.
Programmatically Add Value To TaxonomyField August 25, 2010
Notice that the string is formed as a lookup collection of ids and names. In fact the taxonomy filed is a lookup field. However the terms in the Taxonomy do not have an integer id…
Where is this id coming from you may ask?
It truns out the the terms are actually stored on a hiddent list, and the integer ids are the ids of the terms in this list.
If you look at the definition of the field in the list you will see that we have two fields: LookupList and LookupWebId.