 |
| Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
| Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
| Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
 |
|
|
|
|
|
Lee Allen > MOSS KB > Conferences
|
| A blog for conference sessions |
2/4/2009Peter Serzo www.trilliumteam.com
PSerzo@trilliumteam.com
Jquery in action
In CEWP using the navigation (content link)
- Insert text file pnav.txt into the content link field
- This txt file is the actual code for the CEWP That way you can edit it once and use it on multiple web part pages
BP #1 – Save file references at the site collection level
People should never touch the front page. Problems
- No repository
- No approvals
- No maintainability
BP#2 – Limit the use of the CEWP on the Home Page
BP#3 – Limit how much code you put in
BP#4 – Refractor and inline references for maintainability
Jquery is now supported by Microsoft
Blog.jquery.com
Docs.jquery.com
Plugins.jquery.com
Find scott guthrie's blog
BP#5 Use jquery
BP#6 save your Jquery libraries, files, utilities, ect at the site collection level
BP#7 don't write inline Jquery or javascript
There are a lot of web 2.o types of things that are already out there ready to be used
THIS IS GOING TO BE HOT!!!!!!
Paul Galvin paul.galvin@emc.com www.emc.com
twitter pagalvin
Best Practices
- Ace to face interviews
- Be SharePoint agnostic
- Side by side prototyping
Don't!.... roll out all functionality at once
Req, gathering process
- Multiple rounds of interviews
- Demo core features
- Assign homework
- Create prototypes
- Side-by-side review and update
Don't discuss business requirements in context of MOSS features
Business units don't talk to each other much but they have many commonalities (don't ignore these, in fact call them out and bring the groups together)
Avoid intermediaries
Don't rely too much on email
ZZZZZZzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
Yada yada yada
3 types of users
Evan Burfield eburfield@synteractive.com
Takeaways
- SharePoint is becoming THE operating system for the enterprise
- Success involves strategic re-engineering
- Long Term success is a series of quick wins
- The Grass roots are your real stakeholders (End Users Matter most)
- Evolve your architecture
The classic mistake is that we just recreate the same old systems with a new one when we should be understanding the business problem and engineering fresh solutions with the new technology. (example was cows/cow path)
Iterative transformation
Define
- Challenge symptoms to get at root cause
- Define in simple language, not jargon
- Define success metrics
Solve
- Stick to the defined problem
- Understand industry best practices
- Explore other domains
- Innovate and synthesize
- (note) get slide …… for the rest of this info
Start with Business Transformation it drives everything else, it is
- Business vision
- Quick wins
- Grass roots
- Iteration and refinement
- Solution architecture
- Organizational learning
- Politics
Best practices
- Address business problems
- Move fast
- Get close to knowledge worker
- Small solutions are great
- Refine from the simple solutions
- Follow with great architecture
- Training is evangelism
Ruven Gotz www.ideaca.com ruven.gotz@ideaca.com blog http://spinsiders.com/ruveng
twitter ruveng
1st demo was just simple intro to the tool to diagram this conference's topics
MM has a mind of it's own when it comes to positioning. (this takes some practice to get used to, especially if you are used to the control you have in visio)
2nd demo showed a portal "diagram" for the navigation of the site
3rd Demo was to create a taxonomy
4th Prioritization (I really liked this one)
5th Document Inventory Very nice technique to drill down to your document types
The question to ask is not "who can see it", the question is "who should not see it."
6th Brainstorming/Scoping
Don't map "many to many" relationships as it get's too messy.
If you need to get to visio do it at the end.
WOW – good tool…. (note to self ORDER) Balsamiq Mockups ~$79
Once you mock it up…. Don't waste time making a visio wireframe just go mock it up in SP
Funny... "are you still wearing socks, or are they knocked off yet"
Search for Gordon MacLeod's mockups to go templates/examples
Other tools
2/3/2009Pure Q&A
Rubin – IA
Mark – executive governance
Mark – MS – platform
Lauta – web parts
Rob –
Bill – CJ – ADMIN
Mark – tech dev
Q1 - 5 minutes speech to COE– Why sharepoint
- Sell as an emergent foundation technology
- Allows people to control their own files without additional IS so saves cost
From MS
- Next generation in app deployment
- WARNING: SP is a disruptive capability
Q2 – how do we move users from list servers (public folders) to sharepoint?
- This is a search problem
- Or mandate it and move it
Q3 – what is the best practice for staffing requirements
- As a solution – exchange level staffing
- As a platform – think SAP level staffing
(note: these guys don't have a clue about ROI that would sell to executives)
Q4 – what does it take to get a developer up to speed
Q5 – how do you evaluate SharePoint consultants for competency?
- Joel may have blogged this
- Get a 2nd opinion to look over the main consultant's shoulder
- Truly check references
Q6 – how do you deal with the 3 generations of users? (adverse older users, embracing users, young social networkers)
- SharePoint can be carefully configured to meet all
- Email bill@mindsharp.com for presentation on generational users
- Book – when generations collide
"success always comes back to having good requirements"
I was a little late due to some work calls and email. I will want to get the deck for this one
Web parts covered since I arrived
Amanda Murphy
http://blog.funknstyle.com
Amanda@funknstyle.com
Looking at 3 approaches
- SP lists
- Dataform Web Part
- Infopath
Before deciding WHICH ask
What
- Fields
- Total amount of data
- Rules that govern data
Who
- Users completing
- Users accessing
- Permissions
Where
- Field Form available
- Data stored
- Data for lookups
- Template stored
Note: get slides on +/- of each of the 3 techniques
Note to SELF: Learn all you can about Data form web part…. Much better user experience (I know I learned this in designer training…. But I have forgotten it)
Method: create DF WP then export it so it can be used on other pages (best practice)
www.intellium.com
Dan Holme
http://share.intellium.com -> blog
Now is not the time to start a new BI product due to Microsoft's coming new products.
Next office will be available soon (pre beta), probably commercially in 2010 (speculation)
BI Lite
- Tap into Excel/Access data and move to SP
- Present the data with Excel/Access
- Simple (users know these tools)
- Free
Excel
Method 1 from excel (copies as text)
- Format as table
- Export to SP in excel
- Check types
Note SP will take first text field as title
Method 2 from SP - Use new list import functionality
Method 2 from excel
- Format table
- Export to sp
- Check the box so that excel creates a read only relationship
2 options
Once data is moved to SP there is no information retained as where this came from. In other words if you want to know what Office files are linking to the data
WHY
- One truth
- Multiple users
- Alerts
- Versioning
- Recycle bin
- Row level security
Recommendations
- Create and modify the views you need
- Watch out for linked (title field)
- Create list in SP then import (gives you better control)
Nice technique to build formulas is to use the link to SP approach then add your calculated columns in excel to debug
Make sure users know about the task frame in sp and use the print in excel task
When data get's too big for excel use "create pivot table report" in sp task frame
GET THIS DECK ASAP – Too much good stuff to document
Use the alert by view capability
dan@intelliem.com
2/2/2009Good food, smooth jazz, and great company…… and jet engine hand dryers in the bathroom.

Location: Corner of Fifth & F, downtown San Diego Priority Seating: (619)233-4355 Hours: 5:30 pm to midnight Monday-Friday; 10:00 am to 2:30pm for Breakfast & Lunch
and 5:30pm to midnight on weekends. Cuisine: Contemporary American Music: Live Music Nightly
History of Croce's Restaurant & Jazz Bar
Hi! I'm Ingrid Croce and I'd like to tell you how Croce's Restaurant & Jazz Bar began. It was long before my husband, Jim Croce, hit the charts with classics like Bad, Bad, Leroy Brown, Time in a Bottle, and Operator.
Jim Croce was born in South Philadelphia in 1943. We met in 1963 when I was a sophomore in high school and Jim was a sophomore at Villanova University. My band, The Rumrunners, took first place in a folk-singing contest and Jim was one of the judges. We began singing together, fell in love and were married in 1966.
In 1968, we moved to New York City to pursue a recording contract. In two years' time we drove over 300,000 miles playing small clubs and college concerts to promote our first Capitol album, Jim and Ingrid Croce.
Disillusioned by the music business and New York City, Jim sold all but one guitar to pay the rent, and we returned to the Pennsylvania countryside. There we rented a three-room farmhouse, which we fondly called, the "Unofficial Croce's Restaurant." We grew our own vegetables, baked bread and served delicious meals to our friends and fellow musicians who would stop by to jam late into the night. Jimmy Buffet, James Taylor, Arlo Guthrie, Bonnie Raitt and The Manhattan Transfer were among our many guests.
In September of 1971, Adrian James ("A.J.") was born and Jim wrote Time in a Bottle for his son. He also wrote You Don't Mess Around with Jim, the title song to the first of his four gold albums. Over the next two years, Jim embarked on a demanding promotional tour, performing concerts all over the U.S. and Europe.
 In August of 1973, we moved to San Diego. I vividly remember exploring our new home town with Jim, who had just returned after months on the road promoting his music. We stopped on the corner of Fifth and F in Downtown San Diego, looking for a place to eat and a club where we could listen to live music. We were disappointed to find only tattoo parlors, ladies of the night, and people begging for change.
We joked that evening about opening a local restaurant and bar that would offer great food and music like we had done in our own home. But less than a week later, after playing a college concert, Jim's plane crashed in Natchitoches, Louisiana.
Years later, with hopes of keeping Jim's music alive and of building a tribute to his life and music, I was called by a friend who told me she knew of an open storefront for rent in the dilapidated Gaslamp district. When I went to look at the space, I realized it was located on the same corner where Jim and I had stopped a dozen years before. It felt like an omen. Building a restaurant and bar there would be the perfect tribute to Jim and a wonderful opportunity to help revitalize downtown San Diego.
It is here at Croce's Restaurant & Jazz Bar that we continue to pay tribute to Jim Croce and his music by serving delicious contemporary American cuisine and offering live music nightly to friends and visitors from around the world. This is my way of sharing the memories of Jim's warmth and hospitality.
Thank you for joining me. Ingrid Croce
| Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /mosskb/ConfBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /mosskb/ConfBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
|
|
|
|
|