Back at it again. On a side note, I did public transit the last two days to the conference from my brother’s house. This may not sound like a big deal but for me it was. I grew up in the Detroit area and we don’t really have public transportation. To be able to get on the Bart and get to the conference site within a half hour was great!!! I also should mention that I am directionally challenged.
Building an Effective Information Architecture
The session description:
“One of the reasons many SharePoint implementations fail to meet user expectations is the lack of investment in its underlying information architecture. Some organizations see SharePoint as an out-of-the-box solution that they can simply plug in and throw content into, but it requires much thought and effort around data structure and organizational principles. This session will discuss building an effective information architecture strategy for SharePoint, including such topics as: • Building an information architecture vision• Requirements gathering• Implementation strategy and approaches”
I was hoping for more concrete guidance but it was more high level and general lists of requirement gathering.
ECM from a Developer’s Perspective
A few take aways from this:
The presenter likes features for deployment. He cautions that one should make sure they clean up after themselves when a feature is deactivated.
Paul has done this presentation over 20 times in the last two years.
The slide deck is on Slide Share. Search for Paul Swider.
If you really want to take advantage of the Document Id feature, there will probably be custom coding to provide the ability for different prefixes for different types of documents. Out of the box, the document id feature has one prefix that can be used.