I am looking for a document repository solution (hosted internally, not cloud-based) that has the following set of features:
Statuses: Users can set a status (pending, complete, etc) on the document. Notification system based on the status change.
Workflows: Ability to define who the documents go to based on the different statuses. Be able to customize these workflows.
Tagging: Users want to be able to tag different sections of a document with certain key words.
Search: Ability to search for documents based on content within the document as well as for tags.
Merging: Ability to select different pages and/or content within one document and merge that content to another document. Kinda like copy and paste, but more seamless.
Archiving: We need to be able to archive documents in some way.
Permission System: We want to limit document access to users based on roles (read, edit, delete, etc.)
Real-time collaboration: Users should be able to view documents at the same time.
I know that SharePoint has support for at least some of these features, but I am not sure which ones. I am having a difficult time navigating Microsoft's website on what SharePoint can actually do.
So my question is, do you guys know which of the above features SharePoint supports? Oh and any recommendations for other document repository solutions are also welcome.
Assuming that you are targeting SharePoint 2013 on premises;
Status - this can be done by adding a column to document library
Workflow - this is available out of the box. You can also enhance workflow capabilities with adding a third party workflow engine (e.g. Nintex)
Tagging - I am not sure I understand "tagging different sections of a document". Document tags are supported in SharePoint
Search - supported
Merging - this is "document set" functionality in SharePoint. But, it is limited to creating a set of documents with multiple files. Not sure this is what you want
Archiving - Look at records management processes in SharePoint. You can set file retention policies. You can declare records (so no one can change/delete them). Depending upon your definition of Archiving, this may or may not work for you.
Permissions System - most definitely available. More granular than NTFS IMHO
Real Time collaboration - available
Hope this helps
Related
I have a couple different Sharepoint pages (Sharepoint Word docs) all with roughly the same purpose and information, but for management reasons, some of it needs to be restricted from a certain set of users. We keep having to update each page in several different places any time a single change or update is made.
It'd be easier to be able to mark certain tables on a single page with specific permissions. Is that something Sharepoint can even do, though?
Providing you have an enterprise license for on-premise the best way to achieve this is by using targeted audience feature on the webparts.
You could check SecurityTrimmedControl, you could hide the content based on user permission.
https://rijsat.wordpress.com/2016/10/27/security-trimmed-control-in-sharepoint-2013/
I have created a Document Set in SharePoint online and allowed the Document content type to the document set.
Is it possible to restrict the types of documents uploaded to the document set? I only want users to be able to upload Word 2007 documents and above and not any older versions of Word documents such as Word 2003.
Not sure if it is possible or not? I can't see of a way to restrict this from the content type or document set.
This is not possible using Out Of The Box (OOTB) SharePoint. I am assuming you don't have access to Central Administration.
Event handlers are a common approach but you need to a have good reason to incur the technical debt involved.
Here are some discussions of options on how you can do this if you really feel it is worth the risk and trouble.
https://sharepoint.stackexchange.com/questions/1039/how-to-restrict-a-document-library-to-a-specific-file-type-extension
https://social.technet.microsoft.com/Forums/windows/en-US/313c37ca-62cd-434f-9fe8-3eacc4044a63/can-we-restrict-specific-file-type-uploading-on-sharepoint-library?forum=sharepointgenerallegacy
I'm trying to find a better way to organize a huge mass of documents on SharePoint 2013. I've done a lot of searching and I thought that Enterprise Metadata would be my solution but I have yet to find a good way to harness it. I fell like there must be a solution to what I need built into to SharePoint already.
I want to give each document a "tag" or Enterprise Metadata Keyword and then have a document library that only displays files that are associated with a specific keyword. Any ideas?
Thanks!
I'd suggest some built-in SharePoint document library features to consider to start with, before looking at any third-party offerings.
For a document library, (via the settings for the document library), you can enable Metadata Navigation Settings - this can allow a user to filter list items based on metadata fields. This may offer something along the lines of what you described. I'd advise caution for large lists though.
Another option would be to look at creating or amending views for the library - the options are found on the Library tab of the ribbon. You can setup some filtering or aggregration for the view.
There is also the option, if appropriate to make certain views only available at specific locations within the document library - set via the per-location view settings
I am trying to set up dynamics for a call centre that just wants to do cas management. How do I turn off these things off so there is no evidence of them for a user of the system?
A good place to start would be to edit the SiteMap.
There is a project on codeplex which might be helpful, otherwise you can find good guides dotted around the place:
Editing the SiteMap
Editing the SiteMap 2
With this you could hide Sales & Marketing, which would be a good start. You may also want to look at amending permissions for Leads/Opportunities which can be done by editing security roles. This will help nosey/inquisitive users from creating records if they find links elsewhere.
I presume that you are referring to the subsections of the native CRM navigation structure which shows Workplace, Sales, Marketing, Service and Settings.
Visibility of these areas can be driven in two different ways. You may choose to employ both methods.
Firstly record-type visibility is governed by a user's permissions. Remove a users read access to Invoices for example and it will cease to appear as a navigable option in their UI. Similarly the sub-areas that I previously mentioned will cease to appear if a user has no access to any of the record types that it contains.
consequently it may be possible to achieve some of your aims by giving users the least possible permissions required to do their job (though you should be doing this anyway really) by granting the correct ouot-of-the-box roles or cloning and customising one of those roles. The problem is that the Sales section , for example, contains record types that your users will need to see, e.g. contacts. you won't be able to revoke access to contacts so you'll likely need technique #2 as well:
The CRM sitemap can be customized to contain whatever you want and can even contain new areas. One feature available is to alter or create rules that show/hide areas based on record permissions. I'd recommend downloading the Visual SiteMap Editor and read this part of the CRM SDK
We are researching the various options that exist in our environment to create an Employee Directory. We have a SharePoint portal, AD and recently moved from Lotus Notes to Exchange. Our current employee search is a custom Notes DB that has since been retired.
Since moving to SharePoint an year ago, we've used a custom list using SharePoint Profiles that are updated from AD. But the simple list interface isn't very user friendly and is very slow. Sone of the requirements include type-ahead, pictures, and details of skills/certifications and other demographic information etc. We are considering building an ASP.NET or SilverLight application that can consume the information in the SharePoint list. With the introduction of Outlook and the Global Address List, we are now wondering if it might be easier to build something within Outlook.
Has anybody traveled a similar path and what would you advice us to do?
Microsoft has a huge set of offerings for Collaboration and Social Computing in Sharepoint.
See this document, pages 8 and 9 for information about features related to an employee directory, including details of skills/certifications and other demographic information.
A la carte availability of individual features (such as People Profiles and People Search) and pricing may be an issue, but you may want to look into buying something rather than building it (if you can get the pieces you want for a price you can afford).
Sharepoint can connect with Outlook to keep the lists synchronized if you want to use outlook. And there are definitely a lot of different ways to change the way the lists are presented in the Sharepoint portal to make them more user-friendly. Having those details on the portal will certainly be a boon when combined with the powerful search and indexing features in SharePoint so you can identify employees based on their profile details easily.
We use the people search for this pretty effectively. We populate data in AD, then connect profile properties to AD attributes. That's only if you have MOSS, though. If you're working with WSS, you'll have to build something more custom.
One gotcha, though, is that the People Search out of the box doesn't easily do partial searches (i.e. searching for "john" doesn't match "johnson"). That's a big downer in my mind. You can use Ramon Scott's approach of a Content Editor Webpart with a form and some Javascript to work around it, and you can also get there via the advanced search box (albeit indirectly), but it sure would be nice if it were easy to make the default search box do partial name searches.
I recently just discoverd a somewhat easy visual basic script that draws information from the active directory where you can specify which OU to draw from where it displays all user information in a simple .HTM page. it includes a search bar, recognizes patterns (address) (company telephone number) etc... If you would like i can post it for you. you only need to fill in a few sections (display name for directory, OU, OU display, and tags) and you can always change the way things look too.
This should be taken care of by using the My Site feature that's available within SharePoint. You will then be able to search SharePoint users by skills, certifications, projects, and educational qualification.
Please refer to the SharePoint Planning and Deployment material on TechNet for more info.
SH.