Reading a column from a Sharepoint list element

Even the title is rather complicated... Solving this took quite some time. Extracting one field (=column) of a specific list element in Sharepoint is what I need to do. This should be done to use the information in another application. I checked online but couldn't find the best way of doing it. One promising way seems to use an XML View of the list - this can easily be exportet.

This is how you create it - and call it from your browser:

http://{0}/_vti_bin/owssvr.dll?Cmd=Display&List={1}&XMLDATA=TRUE
{0} – The URL to your site.  This could be the root web or a child site.
{1} – The GUID for your list.

Example:

• GUID for my list: {F24D7439-1A5F-41E1-9E0D-2BD39151C33F}
• http://sharepoint/MyList/_vti_bin/owssvr.dll?Cmd=Display&List=%7bF24D7439-1A5F-41E1-9E0D-2BD39151C33F%7d&XMLDATA=TRUE

You may want to limit the number of results using a custom view:

• GUID for my specific view: {968A1E8C-25E6-4801-93D9-412E85B3ABFE}
• http://sharepoint/MyList /_vti_bin/owssvr.dll?Cmd=Display&List=%7bF24D7439-1A5F-41E1-9E0D-2BD39151C33F%7d&View=%7b968A1E8C-25E6-4801-93D9-412E85B3ABFE%7d&XMLDATA=TRUE

There are many different ways of achieving this. An alternative is the business connectivity Services: http://msdn.microsoft.com/de-de/library/ee557658.aspx

or reading directly from the SQL database: http://www.codeproject.com/Articles/14232/Useful-SQL-Queries-to-Analyze-and-Monitor-SharePoi

This should be done with caution - and only if it is at all necessary (reasons: performance, licence violation, instable primary key).

EDIT: this is another way of achieving what I was looking for: http://msdn.microsoft.com/de-de/library/ff521580.aspx
The MSDN article descirbes how you read a value of a field in a Sharepoint list using C#.

Integrated Knowledge Management Framework

As part of my master thesis I developed a framework for the successful implementation of an IT-driven Knowledge Management project: the introduction of an Expert System for the Support organization.

This is based on the combination of practical experience as a project manager of the introduction of an expert system at a medical devices manufacturer and theoretical considerations provided by Amrit Tiwana in his book (The Knowledge Management Toolkit: Practical Techniques for building a Knowledge Management System, 2000).

The derived model consists of four phases. The resulting framework combines the benefits of both worlds: theory and practice.

PHASE I: IS-ANALYSIS
Where are we – and where should we be?

• Alignment of Knowledge Management and Business Strategy
• SWOT Analysis
• Analysis and audit of the existing infrastructure and processes
• Benefits, needs of a KM initiative (measure ROI)

What is our goal – and how will we reach it?

• Project Goal Definition
• Project Management (time, budget, quality, risks, identification of stakeholders)
• Design the KM Team (expertise, organizational structure, responsibilities)
• Rough Requirements analysis

PHASE II: KM SYSTEM IDENTIFICATION
What should the perfect solution look like?

• Create the KM Blueprint (incl. make or buy decision)
• Content Selection
• Conduct a Detailed Requirement Analysis (RFP, including Use cases and Requirements)

Which vendor proposes the best solution to our requirements?

• Evaluate the KM Systems (RFP results, references, demo accounts, “Beauty Contest”, Presentations)
• Conduct a pilot project
• Evaluation of the pilot (surveys, user interviews, key-user feedback)
• Decision on vendor

PHASE III: DEPLOYMENT
How can we deploy the system?

• Conduct contract negotiations
• Perform System Deployment (Installation, Configuration, Customizing, Training, Testing)

How can we improve culture and adapt processes?

• Manage Change, Culture and Reward Structures
• Roll-out and ongoing user support

PHASE IV: EVALUATION AND REFINEMENT
How did it work out?

• Evaluate Performance
• Perform Lessons Learned

How can we move on from here?

• Incrementally refine the KMS
• Launch additional KM Measures

Feel free to add your comments.

The Knowledge Management Toolkit

According to Tiwana in "The Knowledge Management Toolkit" (2000) there are some necessary steps for successful knowledge management:

1. Identifying knowledge gaps
2. Creating a culture of knowledge sharing
3. Creating appropriate metrics
4. Developing communities of practice
5. Diffusing best practices
6. Training
7. Structuring processes
8. Removing knowledge sharing barriers
9. Aligning local knowledge
10. Creating process triggers
11. Making knowledge management a part and parcel of routine work

In addition, he favors solutions that leverage the intranet as it is at the heart of any business. Do these still look relevant 12 years later?