Re: All file server files to WSS 3.0 system ? (Was newbie simple questions (1))

Tech-Archive recommends: Fix windows errors by optimizing your registry

Watch out for multiple selection columns/fields. They are not as good as they seem.

For instance you can't sort on them.

Do at least some testing with them before you decide to go for them. I find them *occasionally* useful but because of the limitations, not very often.

Enjoy your holiday.

Mike Walsh

Felipe M. wrote:
Yes, i've looking around the previous link http://www.wssfaq.com you
provide in your first reply.
Its pretty clear when you see a demo. Thanks.

I keep playing, i see that i can add new colums- metadata of type
"multiple selections with checkbox", so i could allocate a document in
two categorys in the same library (a document belonging to 2 o more
categories or belonging to 2 o more subcategories).
This can't be done in a Windows File Server (a file belongs only to a
folder). In WSS, however i could get that way (defining new colums
with more than one value at the same time, using chekbox)
The problem with that is that i see thay i can not make views grouping
by this field (with multiple values).
I suppose that this must have a sense. For me is a lack and this
momment. I keep trying.

Thanks to all your replies, dont' make a effort to reply me again
because tomorrow i go on short holidays, and you 've helped me enough,
and this question should have a new post (and because if you reply
soon i will quickly post another question, i suppose till i kwow
everything about WSS or my plane take off. :)

Thanks really,






On 28 nov, 14:42, Mike Walsh <englantilai...@xxxxxxxxxxx> wrote:
Glad to be of help.

For a simple look at how different views can be useful look here

http://wss.asaris.de/sites/walsh/Lists/Articles%20for%202007%20Produc...

(it's a WSS 2.0 based site but it's the same idea in WSS 3.0)

There are views that are based on Categories and/or Sub-categories;
Views based on whether a particular Yes/No field has been selected or
not; and the more usual views showing all documents but based on sorting
on different fields.

You can also see examples of Grouping (and I think some of those are
expanded by default (show heading and contents); and others non-expanded
by default (show headings only at first).

(I'm not using IE so all of them are then expanded)

Mike Walsh



Felipe M. wrote:
Ok, Mike
I think i almost understand everything. (evererhing of the begining)
Users must use the WSS web environment to find its documents, using
"search" or using created views in document libraries.
Another thing doesn't make muchs sense.
To save /create a document is enough to:
- use upload document from the web interface (your actual experience)
- Or use "save as" , choosing the suitable document library
In both cases, i will be asked to establish the different metadatas
defined in my document libraries. So, the document can be found using
the document libraries views.
I've being doing some trials and i think i can sub-gruop document
libraries using views and that i won't need more folders at all!
I think i'm starting to undesrtand how to use /store/find document in
WSS (and the advantages), it's a different way that a File Server.
Even more, thanks to document libraries views i will be able to have a
"multi-clasified" system to group/find/filter documents. That seems
fantastic.
I keep learning.
Thanks for your help,
On 28 nov, 12:06, Mike Walsh <englantilai...@xxxxxxxxxxx> wrote:
I never use File SaveAs to save documents to a document library as I
prefer myself (and my users) to use upload document.
Then you get the chance to add the metadata you need so that the
document gets assigned to a particular View (simple example: three views
HP, IBM, Microsoft so you have a field Supplier of type Choice with
those three alternative values which is completed on upload).
I suspect you also get asked to provide metadata when you Save a
document to a document library, but someone who does this should confirm
this.
Mike Walsh
Felipe M. wrote:
Thanks for the answer Mike,
One questions related with your answer: if i define document libraries
with views insides as you suggest me to avoid using folders/nested
folders ("sub-group" files)
i wonder what will be the behaviour with office application users in
this scenario when these users don't use the web interface.
If they use "File -> open" in Word, of "File --> Save as", how the
interact with views created inside document libraries to find their
documents?
(as you may guess i 'm thinking about folders/nested folders and my
mind can avoid it, does WSS atempt to finish that way of manage
documents?
Really newbie questions,
next time, i'll make better subject.
Thanks,
Felipe Millan,
But if i use more than one library, trying to avoid having just one
document library
On 28 nov, 07:20, Mike Walsh <englantilai...@xxxxxxxxxxx> wrote:
(Just a warning - this newsgroup is not for MOSS questions)
You should not blindly put the files from a company file system in a WSS
3.0 system. That is never a good idea.
For instance most people who have used SharePoint for some time will
advise you against using folders within document libraries (instead use
views), yet the recommended max. limits that Microsoft give are 2000
files per folder and 2000 folders per document library. So if you don't
use folders you have "only" a limit of 2000 files per document library.
In any case it is a bad idea to have only one document library. You are
started off with one document library but the idea is that you add more.
Another point is that some file types can not be stored in document
libraries. These are file types where for instance it is necessary to
have a number of files in one location (link files for instance) before
a file can be opened in the application.
Then there are some files that could be stored in a WSS 3.0 system but
for which it is not a suitable place. These would include very large
files like CAD and video files.
What instead you should do is evaluate all your 10000 files; decide
which ones you no longer need; exclude ones that oughtn't to be stored
in a WSS 3.0 system and then on the files that are left do analysis to
decide how to group them (in different document libraries) and sub-group
them (in views in document libraries).
(Finally please give meaningful subjects - I've renamed this one)
Mike Walsh
WSS FAQhttp://www.wssfaq.com
no questions by e-mail please
Felipe M. wrote:
Hi everyone.
Some basic newbie questions. (i'm new in wss & Moss).
Maybe here i present wrong concepts, so, take care of newbies like me,
don't get confused because of reading next questions. i'm trying to
undesrtand what WSS is for, how to use and develop.
Here i go.
I'm thinking about passing 10.000 files (all the documents of a
company file system) of a W2003 File Server to a WSS environment.
My questions are the following:
1. Is it a good idea that all the documents of a company to be in a
WSS environment instead of being in a File Server? Is this a common
practice??? (are companies doing this???) Or is better that WSS just
manage some documents because of its collaborative characteristics,
and the rest of the documents (most of them) being served with a
clasic Windows File Server?
I mean, any problem if:
- Previous situation (actual):
10.000 files in File Server
- Future situation:
10.000 files in a WSS environment (all the documents).
If there is no problem about it, my second question would be:
2.- Should end /final user use the web interface of WSS?
I mean, i think most of my users should not realize of the IT change
to WSS.
They should continue using Word, Excel, etc, .. and File --> Save
As ... withouth knowing what's beyond (WSS or a File Server).
I think that using web interface is slow sometimes, specially for
those users who don't need new WSS funcionalities.
So, any problems if my 10.000 files go to WSS (in a first step to a
single Document Library), and my users keep using from Office
products:" File --> Save" as as they used to do until now?
thanks in advance- Ocultar texto de la cita -
- Mostrar texto de la cita -- Ocultar texto de la cita -
- Mostrar texto de la cita -- Ocultar texto de la cita -
- Mostrar texto de la cita -

.

Relevant Pages