|
|
 | | From: | Java script Dude | | Subject: | Clarification of document management verbs | | Date: | 14 Jan 2005 11:28:31 -0800 |
|
|
 | Greetings,
I am interested in finding out how people are using the following verbs
in their document management deployments: Checkin, Checkout, Upload and
Download.
>From my perspective the following is clear and concise:
Upload: Copying of a file from ones local computer to a repository on a
main server. No unlocking of file on server is performed.
Download: Copying of a file from a repository on a server to a local
computer. No locking is performed on the server.
Checkin: Assumes that a lock is already made on the server side
repository. File is uploaded from ones local computer to the server
side repository and the lock is removed on the server.
Checkout: Assumes that the file is not already locked on server. File
is locked on the server side repository and is downloaded from the
server to the clients personal computer.
Unfortunately, we currently use Matrix One which merges the words
checkin and upload into the same word. I consider this a rather
significant flaw in their UI designs and is an impediment to deploying
document management systems onto the more general public.
Thanks for your time and interest.
TCQ
[Saving verbs version and revision for another post :]
|
|
| | From: | Java script Dude | | Subject: | Re: Clarification of document management verbs | | Date: | 15 Jan 2005 07:11:36 -0800 |
|
|
| Thanks for the reply,
The diffictulty with making the verb check-in with the verb upload is a
training and UI issue. When a user does not have a file locked on the
server and wishes to overwrite that file, the user is just uploading
the file. If the file is locked and the user does not unlock the file,
it is still just an upload. If the file is locked and the user unlocks
the file, then it is a checkin.
This logic is based on the first law of singularities: If a check-out
is a download+lock then a check-in must be upload+unlock.
It also would make it easier to communicate with the users by asking
the question `did you check-in the file?` you are asking did you upload
and unlock as opposed to `did you check-in the file and unlock it?`
Maybe I am over analyzing but I do want to make my system as intuitive
as possible.
|
|
| | From: | Russell H | | Subject: | Re: Clarification of document management verbs | | Date: | Mon, 17 Jan 2005 10:33:14 -1000 |
|
|
| Do you really want to separate the upload/check-in? From a user's point of
view I don't see a difference between an upload/overwrite of a document that
hasn't been checked out, a new document check-in and a normal check-in.
Yeah, it makes a bit of difference to your system, but that's your problem,
don't make it the user's problem.
As for the difference between download and check-out, the difference is in
if you're just wanting a copy or if you're going to edit the document.
Download gets you the document, check-out sets the lock and gives you the
option to download. (At least that's how I've seen it on some systems.)
Bottom line, I see a download, check-out and check-in functions. "Upload"
is pointless and confusing. If you want, you can rename download to
"retrieve" just so people don't ask about a reverse function.
One last thing, I haven't seen or at least noticed any system that allowed
the overwrite of a non-checked out document. For one thing it can be a bit
difficult to identify to the system what document you want to overwrite.
What I've seen is that when you check-in, it asks if this is a document that
you've checked out or a new one. That way you have a list to pick from, not
having to identify it by hand.
"Java script Dude" wrote in message
news:1105801896.012336.118310@c13g2000cwb.googlegroups.com...
> Thanks for the reply,
>
> The diffictulty with making the verb check-in with the verb upload is a
> training and UI issue. When a user does not have a file locked on the
> server and wishes to overwrite that file, the user is just uploading
> the file. If the file is locked and the user does not unlock the file,
> it is still just an upload. If the file is locked and the user unlocks
> the file, then it is a checkin.
>
> This logic is based on the first law of singularities: If a check-out
> is a download+lock then a check-in must be upload+unlock.
>
> It also would make it easier to communicate with the users by asking
> the question `did you check-in the file?` you are asking did you upload
> and unlock as opposed to `did you check-in the file and unlock it?`
>
> Maybe I am over analyzing but I do want to make my system as intuitive
> as possible.
>
|
|
| | From: | Russell H | | Subject: | Re: Clarification of document management verbs | | Date: | Fri, 14 Jan 2005 18:47:09 -1000 |
|
|
| I'd say that Upload/download is the transfer of a file - no lock information
is implied. In your definition you are explicitly saying no lock is set,
I'm saying that it's a straight file transfer.
I suppose a case could be made that check-in/check-out is more of a locking
situation. While the file usually is transferred, that's not always
implied. When you say a document is "checked out" you are saying it's
locked.
Offhand I don't see a problem with upload/check-in being combined. Even if
the file is brand new, a check-in process is required to index and identify
the file. If no file is being uploaded, then you really aren't checking
anything in, if anything you are canceling a check-out.
"Java script Dude" wrote in message
news:1105730911.879396.276550@c13g2000cwb.googlegroups.com...
> Greetings,
>
> I am interested in finding out how people are using the following verbs
> in their document management deployments: Checkin, Checkout, Upload and
> Download.
>
> >From my perspective the following is clear and concise:
>
> Upload: Copying of a file from ones local computer to a repository on a
> main server. No unlocking of file on server is performed.
>
> Download: Copying of a file from a repository on a server to a local
> computer. No locking is performed on the server.
>
> Checkin: Assumes that a lock is already made on the server side
> repository. File is uploaded from ones local computer to the server
> side repository and the lock is removed on the server.
>
> Checkout: Assumes that the file is not already locked on server. File
> is locked on the server side repository and is downloaded from the
> server to the clients personal computer.
>
> Unfortunately, we currently use Matrix One which merges the words
> checkin and upload into the same word. I consider this a rather
> significant flaw in their UI designs and is an impediment to deploying
> document management systems onto the more general public.
>
> Thanks for your time and interest.
> TCQ
>
> [Saving verbs version and revision for another post :]
>
|
|
|
