SharePoint People Search on office location - sharepoint-2010

I am working on a solution to allow users to search for other users, since we use SharePoint 2010 and have access to the SharePoint people search it seems like an easy solution. For the most part it is close to what is needed but it appears to be missing a few things.
The biggest thing is the ability to search by office/location.
The search appears to return the office location but I can't seem to search on it.
I expected to be able to search on it by doing BaseOfficeLocation:"Office Location To Search For" since Department:"Department To Search for" appears to work.
I have tried Office and OfficeLocation but it just doesn't seem to work. I found a blog that said that it appeared as if this didn't work as expected but there were no more details.
Is there a setting that I need to enable or do I need to do some custom development here?

This might be a little late but here goes.
You basically need to add a metadata property that maps to the office (or whatever) field on the users profile. You then need to have that crawled. Finally you can add office to the search option. Below give you a quick overview of how to do it.
Adding a new managed metadata property
Go to Central Admin.
Go to manage service applications
Go into your search service application
On the left under "Queries and Results" go to "Managed Metadata Properties"
Click "New Managed Property"
Give it a name, I called mine "Office"
Click "add mapping" and select people
Select "People:Office(Text)" (this depends on which field on the profile you are using to put the office in)
Select "Include values from a single crawled property based on the order specified"
Click OK
Now run A FULL CRAWL. That's quite important. If it's not a full crawl it wont be picked up.
Wait for the full crawl to finish.
Adding the field to the search
You should now be able to search for Office:"office name"
That's not very useful to a user
What we want is to add it to the search options
Edit the page and go to the web part properties for the search box
Go to "Miscellaneous" and expand it
Open up "Properties" and copy out the XML. Here you now need to add in your new field.
It's going to look something like this:
<Property Name="Office" ManagedName="Office" ProfileURI="urn:schemas-microsoft-com:sharepoint:portal:profile:Office"/>
Add that in and then save it back into the web part
Click on search option, type in the office in the new office field and click search
BOOM!! Office searching.
Unless I'm missing something you're going to need to do this on both the initial people search page and the results page.
Here's a link that i based that all on.
http://blogs.technet.com/b/meamcs/archive/2010/12/23/sharepoint-2010-people-search-using-metadata.aspx

Related

JIRA: How to get search box to remember project code?

I use the search in JIRA about 50 times a day and every time it forgets what I just entered. Is there any way to tell it to remember the last search or the project code. (By project code I mean the first few letters of bug code such as "AAQT-").
That prefix is known as the project key.
(Also, what version of JIRA are you using? There are some UI differences between Cloud and most Server instances so my following advice might not make sense.)
There isn't a way to pre-define the project key in the quick search box since most JIRA instances have multiple projects, and pre-defining it for just one project doesn't make sense.
However, your browser should be able to remember previous values entered. You would have to overwrite the numerical portion that follows the key, though.
Do you mean save your search as your favourite filter? If so then you can follow these steps :
Click on "Issues" dropdown then choose "Search for issues"
Click on "New filter" button on the top-left area
Type your query
Click on "Save as" button on the above of query field
Give any search name, then it will be save under "Favourite Filters" section

Can't find the workflow source code of a list or library on SharePoint Designer

I'm new using SharePoint. I am having trouble with find the code or workflow structure of a list or a library. In the left menu i can see the "Workflows" button but all workflows are not there.
There is a workflow section In the "List and libraries" view showing the running workflows in these list, but when i click on one of them it just move me to its settings in the browser and no to the structure or code that is what i'm looking for.
Is there a way to find the code or structure of my running workflows?
PD: I am working in place of the previous developer who build the entire site, however, he didn't show me anything about.
Thanks.
If these are workflows created using SharePoint Designer then:
Open SharePoint Designer
Open the site
Click on Lists and Libraries
Click on the list name
There will be a heading titled "Workflows"
Click on the workflow you are wanting to look at
Click "Edit Workflow" to view it
Go From there
If you are wanting to see the status of a workflow in regards to the item:
Go to the list
I recommend creating a personal view (so only you see it)
You can select the fields you are interested in and each workflow should have a column in the list associated with it. Include the column in your view
Go to your new view and you can click on the link to view the current status of the workflow
Go to All Files > Workflows Folder. Then select the workflow you want to work with. Right Click on the "xoml" file then select "Open With" > "SharePoint Designer (open as workflow)"
Once it's opened, published it again. Then it will show up again in the Workflow tab.
The workflow was a visual studio sequential workflow deployed in the site as a feature. It was not a SharePoint Designer one. Thanks

DMS Document option disappearing from New menu on folder in Ektron 9

Ektron 9 - steps to trigger issue ... we think:
Create new content folder
Edit folder properties
Smart Forms tab - untick inherit, and remove "Blank HTML"
The "new" menu on the folder now:
Does not show DMS Document as a menu item
Does not show Smart Form list as a pull-out sub menu.
Question
How do I get "Blank HTML" back into the smart form tab property in the folder
Why is this happening
Help!!
[Edited] Workaround
eGandalf gave the simple answer via Twitter (previously I had attempted a workaround of putting inheritance back on then resetting the tree): toggle the "Require Smart Forms" checkbox on the "Smart Forms" tab and the Blank HTML option will come back.
This is by design. When you remove the HTML option, note that it checks the "Require Smart Form" box (and, reciprocally, checking the Require Smart Form box removes the HTML option). That means that all other types, including PageBuilder, DMS documents, or HTML are now forbidden in this folder.
As a best practice, you shouldn't be mixing types in a folder anyway. A lot of people do, but that doesn't make it any more valid. If you've got a folder for Press Releases and you have a Press Release Smart Form, you shouldn't have any other type of content in that folder. The less you mix types, the less filtering you have to do either with the API or post-request via LINQ. As a result, you'll have a more consistently performing site.
In situations like this, where I want the DMS assets and the Smart Form content to a) both be searchable, b) both be managed by the same user/group and c) there's a strong connection between the two (e.g., Whitepaper information Smart Form + PDF asset download), I'll create a child folder and allow DMS assets there. In the Case Study example, the folder structure may look like this:
Content
Case Studies (Smart Form only)
Downloads (DMS Allowed)
In contrast, if I don't want the DMS assets to be independently searchable, I'll remove them from the Content folder entirely and place them in a separate, root-level, non-searchable folder called Resources or Downloads.
Because Blank HTML is a default (and ID 0), you might have to reassign it in the database.
My guess is that removing the Blank HTML option impacts DMS retrieval in the workarea specifically.
In this case, I'd reach out to support, I've never actually needed/wanted to do this.
Edit:
I dug a bit more to try and give you something to try.
You'll need to reinsert an xml_id into folder_to_xml_tbl.
insert into folder_to_xml_tbl VALUES(your_folder_id, 0, 1);
Ektron support have replied:
Hi ,
Engineering have advised that DMS documents are unstructured.
By forcing all content to be structured content, it disallows raw html as well as dms assets and only allows documents with structure to be created
In any reply please include the case number in the subject line.
To open a new case email uksupport#ektron.com or use the support request form at http://www.ektron.com/Resources/Support/Contact/

TYPO3 Where is "Alias" field?

According to the TYPO3 manual:
Where is the Alias field?
Alias field in TYPO3 page properties The Alias field can be found in
the page properties. Here it is located on the so-called "second
options palette", which is not visible by default. To show this
palette, you need to check the "Show secondary options (palettes)"
checkbox at the bottom of the page properites form.
In recent TYPO3 versions (eg.. 4.5.2) the Alias field is located in
the page properties, tab "Behaviour" and is called "URL Alias".
Here's a screenshot from the page properties how I see them:
But where is the "Alias" field in the version we are using? (TYPO3 Ver. 4.5.19).
Even if I put the Type of the page to "Advanced" instead of "Standard". I get a lot more tabs, but not the "Behaviour" tab. In the access list of the user group, everything is checked and the user has full admin rights.
Your properties form on the screenshot lacks many common fields and tabs, apparently you logged in as a common admin without access to it. (see typical form (4.6.x) for compression)
Log in as a full admin and check if these fields are available.
If not that means, they where disabled with PageTS/UserTS
If they are available for full admin and you need/want to enable them for common editors as well you need edit access lists of the editor's group and by selecting proper Allowed excludefields
It might also be worth noticing that there is a difference between the "Live" and "Draft" workspace. It may not show up in the Draft workspace whereas it does show in the Live workspace. Just noticed this recently.

Display QuickLaunch on WebPartPage in sharepoint 2010

I'm trying to work out how to get sharepoint 2010 to display the quicklaunch on a web part page, the default.master trick I used in 2007 doesn't appear to work any more.
In my 2007 install, I simply edited the default.master and moved the quicklaunch code outside of the PlaceHolderLeftNavBar element but this doesn't have any effect in SP2010.
Thanks
A simple way to eneble Quick Launch Menu on WebPartPages is remove tags UIVersionedContentUIVersionedContent and PlaceHolderLeftNavBar using SharePoint Designer 2010.
See this article: http://denmartins.wordpress.com/2011/05/07/exibir-menu-quicklaunch-em-webpartpages/
If you really want to place another copy of the quicklaunch on a web part here is the steps
Using Sharepoint Designer 2010 go to your site and navigate to Master Pages -> v4.master
Click edit file copy everything in the <div class="ms-quickLaunch"> that should copy everything you need for the quicklaunch to run. For best result use the code view and hover over the quicklaunch and you should see the div, click on it and copy (Ctrl + C)
Now you can paste that on another web part page and it should work, I tried it by creating a new test page and it worked
You need to make changes in v4.master (in masterpage library), not in default.master.
For details on SharePoint 2010 master pages, please, follow this link:
http://sharepoint-sandbox.com/index.php?/Tips-and-Tricks/Customization/tip-80-sharepoint-2010-new-masterpages.html
Your masterpage trick on my SharePoint Foundation 2010 environment works fine.
Anyway, I don't think, that moving any standard code from placeholder is a good idea. If you want change position of quicklaunch menu, you should move the leftnavbar placeholder itself, including all the contents.
Placeholders are generally used to allow some pages, for example application pages, replace placeholder contents. So, if you hide the placeholder, and move it's contents out, these changes will be lost, and the standard menu will be shown. (and if you do not hide the placeholder, you can get two menus on one page :) )
Hope it helps!