Uh ... is OneNote 2007 good with sharepoint ... or not ?

E

EMRhelp.org

====
Then Microsoft OneNote 2007 was released, sporting a new "shared
notebook" feature. With OneNote, you get the same ease of access and
ease of editing that a wiki provides, but with a much smoother
experience. To mirror the history log functionality of a wiki, you can
store your shared notebook in a versioned SharePoint document
library.

source - http://flimflan.com/blog/MigrateFromFlexWikiToOneNote.aspx
====

I thought that Sharepoint wrecked the native OneNote Synching and
brought it down to the level of file synching. Anyone ?
 
X

xTenn

Patrick said:
Nope. It works with SharePoint,

Just to be sure I understand, you are saying that ON syncs down to the
container level with sharepoint as it does without it?
 
I

Ilya Koulchin

EMRhelp.org said:
====
Then Microsoft OneNote 2007 was released, sporting a new "shared
notebook" feature. With OneNote, you get the same ease of access and
ease of editing that a wiki provides, but with a much smoother
experience. To mirror the history log functionality of a wiki, you can
store your shared notebook in a versioned SharePoint document
library.

source - http://flimflan.com/blog/MigrateFromFlexWikiToOneNote.aspx
====

I thought that Sharepoint wrecked the native OneNote Synching and
brought it down to the level of file synching. Anyone ?

That depends on exactly what you mean by "level of file syncing". It is
true that there is no option on SharePoint to update just a part of the
file, so OneNote does need to transfer the entire file any time a change
is made, either on the client or on the server. However, partial access
is only an optimization, and OneNote can still sync just fine without
it, although at a slower rate.

Problems occur when multiple instances of OneNote access the same file
and then some other underlying technology thinks that those files are
the same and tries to resolve the situation without asking OneNote. That
doesn't occur on SharePoint though - there is just one copy of the file
involved, so OneNote is able to detect and merge changes from multiple
users without any problems.

Ilya
 
E

EMRhelp.org

That depends on exactly what you mean by "level of file syncing". It is
true that there is no option on SharePoint to update just a part of the
file, so OneNote does need to transfer the entire file any time a change
is made, either on the client or on the server. However, partial access
is only an optimization, and OneNote can still sync just fine without
it, although at a slower rate.

Problems occur when multiple instances of OneNote access the same file
and then some other underlying technology thinks that those files are
the same and tries to resolve the situation without asking OneNote. That
doesn't occur on SharePoint though - there is just one copy of the file
involved, so OneNote is able to detect and merge changes from multiple
users without any problems.

Ilya

So the answer is that SharePoint *DOES* wreck OneNote's native file
synching.
 
E

EMRhelp.org

In Summary,

OneNote's native file synching capability is NOT compatible with
Sharepoint. File-level synchronization is possible still with .one
files and Sharepoint, but larger files will suffer significant
perfomance issues because entire files need to be transferred, not
just the changes.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top