13

When I try to explain metadata in a SharePoint context I turn my head to a simple document. A document have content as in what's written within the document. But metadata is all around the document The author(s) The date/time the document was created The date/time the document was last edited The version of the document If it's part of a project, the ...


10

Terms are the basic unit or smallest item in Managed Metadata or Taxonomy. TermSet is just a collection of Terms.Like say if you want to create a taxonomy for countries and their cities. Country will become the TermSet (eg:England) and cities will be Terms inside respective termsets ie London will be term inside England. Tags are special terms , they are ...


7

You can try : Library settings -> Imformation management policies settings -> select document from content Types -> Check the checkbox to enable labels and type {version} in Label Format. http://smackwagondesign.com/how-to-add-the-sharepoint-version-number-to-a-word-document/


6

The big difference between Keywords and Terms are that Terms are controlled by you (normally) and Keywords are controlled by the users. Sometimes Keywords are referred to as Folksonomy whereas Terms are referred to as Taxonomy. To use Terms to tag a document, create a custom Site Column and map that to a TermSet (which is a collection/hierarchy of Terms), ...


6

Try the following script: $web = Get-SPWeb http://YourServer/ListLocation $list = $web.Lists["TheList"] foreach ($item in $list.Items) { if( $list.Fields.ContainsField("ddlTest") -eq $true) { $item["Number"] = Get-Random -Min 0 -Max 100; $item.Update(); } }


6

You can use the SharePoint REST API for files and folders to get the metadata (or content) of the file. For your example, the server-relative endpoint URL would be: The file with basic metadata: /my/personal/KIEWB/_api/web/getfilebyserverrelativeurl('/my/personal/KIEWB/Documentos compartidos/notas.txt') The file content: /my/personal/KIEWB/_api/web/...


5

Grouping by a Managed Metadata Column with "Allow multiple values" set to true is NOT possible (it just will not work properly anyway). If "Allow multiple values" is set to false, it works just fine. I just double-checked it:


5

Managed metadata navigation is only available in the classic mode experience. If that is necessary, revert your library in the Advanced Settings to classic mode. Features available only in classic mode The Ribbon The Ribbon itself Certain features available through the Ribbon: Popularity trends Tags & Notes Quick Edit RSS Feed Most Popular Items ...


5

I found a way to fix this. My code, and others provided here, do not work. The schema xml has to be edited, i.e. like this: $w = get-spweb "http://pub.pdogs.local" $l = $w.Lists["Simple List"] $f = $l.Fields.GetFieldByInternalName("MyCustomColumn") if ($f -ne $null) { "$($f.SchemaXml)`n" $f.Title = "Changed via code 2" $xml = $f.SchemaXml $f....


4

Search should do this for recognised file types out of the box. Note that does not include PDF - you will have to install the PDF iFilter to enable SharePoint to search the content of PDFs.


4

I found the best way of accomplishing this was to create a workflow and use the workflow initiation form to capture all the necessary meta data, and then create the document via the workflow itself, inserting the corresponding fields from the initiation form into the document columns.


3

Your question implies that you already know the specific item. That makes it easier to isolate the data you want. Each of the lines shown will return a text response as shown below assuming that these are not "special" fields like choice, lookup, etc. This URL will return christophe http:/.../_vti_bin/listdata.svc/Contacts(2988)/Contact/$value This URL ...


3

Create SPQuery object and set its Folder property and then call GetItems on List and finally loop through the item collection. $spQuery = New-Object Microsoft.SharePoint.SPQuery $spQuery.Folder = $folder; $items = $list.GetItems($spQuery);


3

here is powershell script to list all properties and then how to change them. # Load SharePoint library [system.reflection.assembly]::LoadWithPartialName("Microsoft.Sharepoint") # Connect to the site collection http://SP2010 and store the object in the $site variable $site = New-Object Microsoft.SharePoint.SPSite("http://SP2010") # Connect to the root ...


3

I would continue to use metadata tags but use actual SharePoint groups to limit the permissions. Give each department their own document library where the respective group contribute permissions and other departments have read permissions as necessary. Then you can use a content query web part to roll up the documents and not have to worry about ...


3

Apply metadata to documents when drag and drop a file. There is a bit of hardcoding, but here is what I did and it seems to be working. I am still testing this. If you have a way to get the current listname at runtime that would be brilliant! I have this in a CEWP on the library allitems.aspx page itself. I will move this to masterpage after more testing. ...


3

Some pieces of answers: You canno't use that code to copy to another farm: this uses server-side API, and server-side API must be used on a server of the farm you're targetting. An option to push the file to farm B would be to use from server-side code on farm A client-side API to access farm B. Actually, that code, with privilèges elevation, can only ...


3

With KQL it is only possible to query by day ranges. If you want to use something like DateTime.Now you will have to use FQL instead, see link


3

Haven't done this, but the way I would do it is to make a query to search (f.e. using REST) and ask to return tags as refiners (create a refinable managed property, if it's not there yet). Refiners have a RefinementCount property, which gives an approximate number of hits. Creating a link to search for each refinement result (tag) shouldn't be difficult ...


3

Meta-Data:- It means data about data. Or more precisely more information about some 'information '. In context of SharePoint (whether it's 2013) , in general it is information attached to elements. The different type of values entered for an element in a list or library. First we have columns and values present under the columns is known as "Metadata". ...


3

When I try to explain metadata to my clients, I usually reference Amazon.com example. I show them a typical Amazon site page and show them an ability to search for say, shoes. The I show them different filters available. For example, color, cost, brand name, size, etc. And then I explain that each shoe has been tagged against those labels (tags) which in ...


3

When you create the second MMS2, avoid adding it to the default proxy group. If you do, all web apps will have two MMSs, which should be avoided. My guess is that's what happened in your environment.


3

Finally got it to work using REST API. But it involves additional REST call. Below is the code to Create a folder, from that code we will call the get Folder method to get the folder's ID: function CreateFolder(){ jQuery.ajax({ "url" : _spPageContextInfo.siteAbsoluteUrl + "/_api/Web/Folders/add('/sites/testsite/Shared Documents/...


3

This question is primarily seeking opinions since there is no "right answer", but I'll give my thoughts: Folders are OK. Even subfolders. Just watch your URL limits (and if using OD sync, your Windows Explorer or Office client limits). Let users control how their data is organized and displayed, but offer guidance/best practices. Don't require metadata ...


2

Use following code to get the creation date of folder: item.Folder.Item["Created"]


2

I wouldn't use metadata to do a workaround on permission when you already have item level permission built in. By default your documents inherit site permission and those with sufficient permission can read, update and delete documents. But if you want specific permission on a document, edit sharing the following way. Select Shared With Click Advanced ...


2

If there are things that will need to be permissioned, then use folders in conjunction with metadata. Views can be created to recurse through folders to show information to users. This will automatically security trim the results. Managing item level permissions in a flat lisst of documents is a nightmare and can cause performance issues. So don't think ...


2

The Modified By property is updated automatically by SharePoint each time a version is created with the current logged in user. Looking at the version history will show who edited the document and when.


2

Simple answer: Yes it is forbidden. From my point of view you have following options: Do a proper database migration from 2007 to 2010. Metadata will remain untouched. Do the webclient migration and you can create a PS script that will modify the Created and Modified By fields for you and it will be supported. Look up a third party migration tool that ...


2

You can update system properties (Created, Created By, Modified, Modified By) using code like that: using (SPSite site = new SPSite("Your site url")) { using (SPWeb web = site.OpenWeb()) { var list = web.Lists.TryGetList("Your list name"); var query = new SPQuery() ...


Only top voted, non community-wiki answers of a minimum length are eligible