If I understood well the link you can provide as input for a data source for the QnA maker has to be a ‘public’ one. This means that you can’t have a link to for example a folder on Sharepoint (or even a file on Sharepoint)? So what do I do in that case if I want to make a knowledge base based on lots of information on Sharepoint?
Per the the documentation on QnAMaker, they currently do not support authenticated data sources, such as those on SharePoint. The only way to use documents from SharePoint as knowledge-base data is to download the files manually from SharePoint, and then use QnAMaker's file-upload option to extract the question-answer pairs.
Bear in mind, the files must be in the supported format of .tsv, .pdf, .doc, .docx, or .xlsx. Also, as you've stated 'lots of information', QnAMaker does limit how many documents you can add to the free tier: 3 documents, up to 1MB per. The standard tier, which is $10/month, allows for unlimited documents.
Hope this helps!
i had a project where i have to publish qna pairs from sharepoint to the qna maker. what i did was to create an SPFX application and a web service that had to call the endpoints of the QnAMaker (https://learn.microsoft.com/en-us/azure/cognitive-services/qnamaker/quickstarts/csharp)
it was a bit of a hassle though since updating a qna maker item needs to have a specific string, one wrong syntax and it will cause an error.
Related
Hoping someone could possibly help please.
Quite new to the PnP framework, but I have a template up and running, but I'm drawing a blank on customising the OOTB document library with our own custom content types and site columns. I’ve managed to do it for the initial provisioning process using PnP, but the bit I’m currently struggling with is when a user creates a new document library from either the 'addanapp.aspx' page or through a Modern Page, since that doesn’t use our content types or site columns, that just creates a default SPO Document Library.
I’ve been reading about the ECM Document Library core, List Definitions, Event Receivers and CSOM to achieve what I’m looking to do, but not sure where I should be starting.
Ideally, the outcome I'm looking to achieve is I want any new document library a user creates from a Modern Team Site to use only our custom content types and site columns, not the default OOTB ones.
Any help gratefully received, thanks.
Have you checked the demo ECM.DocumentLibraries?
Here is the general explanation video.
You need familiar with SharePoint add-in(app) first guideline here.
Is Sharepoint my best option to replace an aging network of fileshares? There's approx 1TB of data residing among 3 fileshares (1 DFS, 2 NAS boxes). A document management system is in place for new things - the file shares are now just read-only archives/legacy. Our users would simply need to be able to search for and open the documents.
Users are finding it difficult to locate their documents in the file shares and windows search does not often help. Sharepoint was suggested as something which would play nicely with Office documents (99% of the content) and have a good search facility.
Not being a Sharepoint Developer or having had any training on it, I'm getting a little lost. I have set up a test server to try it out using SP2013. I have managed to index each of my file shares and have created a search page. However, results aren't consistent with the indexted items. I assume I need to somehow get the relevant metadata from the files but I have no idea how to go about this.
Could anyone suggest some resources for help on this subject (my searches have mainly turned up paid-for Sharepoint addons or outdated blogs) and any experience of doing something similar? Also happy for any suggestions on ways to achieve this using other software/platforms.
I went with Microsoft Search Server 2010 in the end.
Sharepoint is basically optimized to be a document manager. I think you don't need to buy or donwload addons.
For your problem, metadata are the key! You need to properly specify the metadata.
I give you the theory of a plan document management in SharePoint 2013 :
https://technet.microsoft.com/en-us/library/cc263266.aspx
A nice introduction to metadata :
http://fr.slideshare.net/gzelfond/document-management-in-sharepoint-without-folders-introduction-to-metadata
Be careful to use the Microsoft documentation for the beginning. From my experience, its difficult to start with this documentation because you have several things in it. There is also good books/ebooks that you can find easily to start well, and probably more simplified than MS documentation.
I'm looking to use Redmine for document management. I know that Redmine is not ideal for this task but there is already a lot of content on the site so I'd like to utilize it if possible.
Redmine currently does not a have great documents module. The files we've uploaded look to be amended on that specific page and it doesn't seem to be able to move to another page (unless you download and re-upload to the proper page).
Idea 1
I see there is a Files section, which could work as a central repository (and you can upload document based on release) however, is there a way to set up a nice-looking 'front-end' page that automatically updates based on new submissions to the Files tab? I envision this front end to be a simple wiki page with the document name, a short description and a links to the file posted in the Files tab.
There are so many documents uploaded to varying pages on the Redmine site. I would only do the whole download and re-upload of files if there was a way to automatically update the 'front end' wiki.
Idea 2
I see there is a DMSF plugin for Redmine. Has anyone used this before and has is solved document management issues? I'd like to hear your feedback. Even if DMSF doesn't totally solve my issue, anything is better than what I have now.
Thanks!
In my opinion DMSF module is a perfect companion for Redmine. We have adopted it in our company. You can easily deal with document versions, webdav access, custom approval workflow, document modifications notification with the extra value of being well integrated with Redmine features (roles, dynamic links in Wiki and issue text and notes).
I'm currently working on a project requesting to integrate or connect Sharepoint to TYPO3.
Share point will somehow replace the fileadmin of TYPO3.
So what I mean by "integrate" or "connect" is the following points:
To display lists of documents from sharepoint on TYPO3 pages through the TYPO3 BE by using some tag or category. In short accessing sharepoints document in the TYPO3 BE.
To be able through TYPO3 to search documents from Sharepoint. And to filter them by type or category. And of course to display the results.
I found some references on the web.
The obvious one was the sharepoint connector SPTools of TYPOTYCOON but it seems dead as there are no fresh news on the website and no activity on the twitter account.
I found also two extensions on the TER (WSS/MOSS Reader and WSS/MOSS Writer) last uploaded December 2010. Surely outdated - Did anyone ever used them? have some feedback?
I found also some references about CMIS and the TYMIS extension but couldn't find it on the TER.
That's why I come to you, hoping you have some solution, useful feedback or lead at least...
Starting in TYPO3 6.0 the new File abstraction Layer (FAL) [1.] was introduced. This gives you the possibility to split the file storage from the files used in TYPO3. As the result fileadmin might contain any number of virtual mount points of any supported storage. Multiple (local, WebDAV) FAL drivers come preinstalled and there is an Amazon S3 driver at [2.]. I am not aware of any FAL driver development for Sharepoint. So this might be up to you to resolve, but these hints should get you started.
Links:
http://docs.typo3.org/typo3cms/FileAbstractionLayerReference/
http://git.typo3.org/TYPO3v4/Extensions/fal_amazons3.git
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.