SharePoint: Extending the DVWP – Part 24: A Note to Readers
Author: Jim Bob Howard
Many of you have pointed out that the later articles in this Extending the DVWP series have been more insightful. I understand that some of the earlier parts have been extremely basic. AND, some of them have not been specific to the DVWP. But, we will be referring to them going forward, and so they are necessary for our purposes.
By Wisdom a House (or Site) is Built
As homeschooling parents, my bride and I have extensively researched education methodologies over the last few years and have come to realize and adopt the wisdom and fruit of what is known as the Classical Model (aka The Trivium). The Trivium is a three-stage process of learning: the grammar stage, the dialectic stage, and the rhetoric stage.
Rhetoric is the wisdom phase of learning, where we begin to take some things for granted. Limitations and capabilities are known quantities and we enter into what Mark Miller referenced as unconscious competence. With wisdom, we articulate abstract concepts to provide concrete solutions to real world problems. But before we get there, we have to have understanding.
Through Understanding It is Established
The dialectic stage of learning is when the student begins understanding the interconnectedness of the various basic concepts of a field of study.
In SharePoint, we learn when to use which type of list or library for a given project. We argue and discuss "what if" strategies. We learn by doing, breaking, fixing. Understanding connotes a level of experience: we know how things work (and don’t work) because we’ve BTDT ("been there, done that"). It’s no longer conceptual head knowledge.
And Through Knowledge Its Rooms are Filled
Until about 50 years ago in the United States, Elementary School was known as Grammar School. For most people today, grammar narrowly (and mistakenly) connotes the study of the basics of language: nouns, verbs, pronouns, sentence types, and so on. But grammar in its truest sense applies to any field of learning. Grammar is the vocabulary, the definitions, the basics of the subject. It forms the building blocks or pegs on which we hang advanced knowledge, understanding, and wisdom.
The grammar of SharePoint consists of knowing the components of the environment: sites and subsites; lists, document libraries, and surveys; content types and site columns; list items, columns and their types; webparts, jQuery, and workflows. Grammar increases our knowledge; we are able to converse in the vocabulary of SharePoint.
Some of you may have found some of the parts of this series to be too basic; too much in the SharePoint grammar stage. And we can argue and discuss their place in the series. But it’s those basic building blocks we use over and over that allow us to work in wisdom. So, rather than assume everyone has the same basic building blocks and glossing over some important aspects that in the end look more like "magic happens," I elected to build out those more basic aspects so I can refer to them in the advanced articles that are coming soon.
Even having done so, I’ve found that many people have expressed confusion over some of the "basic" functions I’ve covered. So, I think there will be room to expand on those sections in future articles.
No Stupid Questions
EndUserSharePoint.com has been a tremendous asset to my ability to perform my job in the SharePoint space and I am thankful for the hard work Mark and Natasha have done to build this community; as well as the tireless help provided by the countless authors who have reached out to help with articles and Stump the Panel consulting.
I have found that there are no stupid questions… except those which go unasked. I have tried to make a point of documenting every new thing I learn about SharePoint, especially if I had to piece together information from multiple sources (including my own trial and error). I figure if I had the question, someone else might be (or will be) asking the same thing. If I can document it and post it to EUSP, it’ll be there when I need it again. And it will be available for others who need it.
I encourage every reader of EUSP to submit your solutions for the rest of us to read. You have gained knowledge, understanding, and wisdom to do the job you do. Share it with the rest of us.
We need your help. I need your help.
Next time…
We’ll get back on track next article by "Creating List Items (for an Audit Trail) with SPServices" as we continue Extending the DVWP.
Author: Jim Bob Howard
Jim Bob Howard is a web designer / webmaster in the healthcare industry. He has been working with SharePoint since March 2009 and enjoys sharing what he has learned. He is a moderator and frequent contributor to Stump the Panel, and answers SharePoint questions on Twitter (@jbhoward) and via email ([email protected]).
- SharePoint: Extending the DVWP - Part 1: Layout Enhancement - Rearranging Columns - Default and Edit Templates
- SharePoint: Extending the DVWP - Part 2: Layout Enhancement - Rearranging Columns - Insert Template
- SharePoint: Extending the DVWP – Part 3: Getting it All on One Line - DVWP Function Action Links
- SharePoint: Extending the DVWP – Part 4: Turning DVWP Action Links into Buttons
- SharePoint: Extending the DVWP – Part 5: Doing Stuff Before Save on Submit - PreSaveAction()
- SharePoint: Extending the DVWP – Part 6: Examining the Form Action Links
- SharePoint: Extending the DVWP – Part 7: Creating a Form Action Workflow
- SharePoint: Extending the DVWP – Part 8: Creating a Form Action Workflow - The After Math
- SharePoint: Extending the DVWP – Part 9: Oops! Failed Setting Processor Stylesheet
- SharePoint: Extending the DVWP – Part 10: Passing Workflow Variables to a Form Action Workflow
- SharePoint: Extending the DVWP – Part 11: Getting More Form Fields to the Workflow
- SharePoint: Extending the DVWP – Part 12: Adding More Form Fields from the Data
- SharePoint: Extending the DVWP – Part 13: Putting PreSaveAction() to Work – Creating Variables
- SharePoint: Extending the DVWP – Part 14: Putting PreSaveAction() to Work with jQuery
- SharePoint: Extending the DVWP – Part 15: User-Managed Dropdowns with Site Columns
- SharePoint: Extending the DVWP – Part 16: User-Managed Dropdowns - Loading Data
- SharePoint: Extending the DVWP – Part 17: User-Managed Dropdowns – Creating a Relationship list
- SharePoint: Extending the DVWP – Part 18: User-Managed Dropdowns – Loading the Relationship list – Part 1
- SharePoint: Extending the DVWP – Part 19: User-Managed Dropdowns – Loading the Relationship list – Part 2
- SharePoint: Extending the DVWP – Part 20: Cascading Dropdowns - Applying the jQuery
- SharePoint: Extending the DVWP – Part 21: Cascading Dropdowns - Three-tier Cascade
- SharePoint: Extending the DVWP – Part 22: Creating Title Based on Other Fields with jQuery
- SharePoint: Extending the DVWP – Part 23: Creating Title Based on Other Fields with a Workflow
- SharePoint: Extending the DVWP – Part 24: A Note to Readers
- SharePoint: Extending the DVWP – Part 25: Using an Audit Trail by Creating List Items with SPServices
- SharePoint: Extending the DVWP – Part 26: Modifying the Edit Template
- SharePoint: Extending the DVWP – Part 27: Adding an Alternate Edit Template to a DVWP
- SharePoint: Extending the DVWP – Part 28: Massage the Remove Template
- SharePoint: Extending the DVWP – Part 29: Modifying Form Action Workflows on the remove Template
- SharePoint: Extending the DVWP – Part 30: Using EasyTabs with Filtered DVWPs to Make Data Manageable
- SharePoint: Extending the DVWP – Part 31: Filling in Default Data on the insert Template with jQuery
- SharePoint: Extending the DVWP – Part 32: Filling in Default Data on the insert Template with Multiple DVWPs
- SharePoint: Extending the DVWP – Part 33: Modifying Total and Subtotal Row Layouts in DVWP
- SharePoint: Extending the DVWP – Part 34: Using Icons for Form Action Links
- SharePoint: Extending the DVWP – Part 35: Putting it All Together
- SharePoint: Extending the DVWP – Bonus: Fixing the Insert Form Action When "No Matching Items"
- SharePoint: Extending the DVWP – Bonus: Creating a Title Based on Dropdowns with jQuery
Jim Bob, I think the issue is not the fact that you are laying the foundations for more advanced bits with the basic articles, but that the series seemed to jump abruptly from fairly advanced content at around article 14 to very basic content. To continue your education thread, I see your series like this: its like having a science book. In this you have a chapter called biology and you begin with laying the foundations of knowledge and then advancing onto some tougher content. However, when you move onto another chapter, lets say Physics, you begin by running through basic mathematics before advancing onto the Physics content because you feel the reader needs a grasp of mathematics before you can handle physics (probably not true, but hey I’m not a teacher :P). In reality, maths would be out of scope for a book on science even if it was important for following what was going on. Otherwise you would have a 800 million page tome encompassing every last piece of knowledge on earth which no one could follow.
Ok, that was a pretty bad way of getting my point across, but in my opinion this should have been separated into two separate series’ rather than one giant one that seems to go off on an enormous tangent before (presumably) it returns to the original, intended content… [or spending ages talking about maths to lay some knowledge for a physics chapter in a science book, if you managed to follow my awful metaphor].
By article 14 you were making the assumption that the reader was a competent sharepoint admin and wouldn’t need their hand held for some noddy stuff. It seemed a bit strange to me to suddenly hand hold for another 5 articles.
Regards
Nathan
Nathan,
Thanks for the thoughtful comment. I think you’re right. For the rest of this series, we’ll spend less time on basics. ;)
Blessings,
Jim Bob
This is such a good series it would be nice to have a cumulative version of it on some web page, or better, in pdf form. Some of us don’t like “clicking around”, we learn by careful reading, re-reading, and lots of underlines & highlight colors of our own making.