WikiHomePage | RecentChanges | Preferences
File Workspace Access (15R)
The Shared-File Workspace (or Community File Repository) allows members of the community to share their work easily. (3U)
- The default CWE deployment has in its setup: ("COP" is used in place of the community, team, CoP or site name below) (40)
- 3 user roles: "COP-member", "COP-editor" and "COP-admin" with their corresponding passwords (3W)
- COP portal (the COP's website or homepage) -- is at /data/cop/COP/www/docroot (41)
- 5 file workspaces are available: "file/pub", "file/resource", "file/work", "file/community" and "file/admin" (42)
- Default Access Policy is set according to the following: (43)
(44)
Special Security Measures (57)
- Note that we are not supporting FTP uploads and downloads. This way, we can make sure that unix level passwords will not be necessary at the user level, thus making our system much less vulnerable to malicious attacks. (58)
- The "Open" (op) CWE 'file/pub" workspace will have a file size limit (on individual file being uploaded via WebDAV) that is set, by default, to 8MB's. (59)
Download (Browser) -vs- Upload (WebDAV) URL Mapping (5A)
- For "Open" (op) CWE's: (5B)
Browse To Upload To Typical Use
------------------------------------ ------------------------------------- --------------------------------------------------------------
Portal:
http://COP.cim3.net http://COP.cim3.net/portal Community Portal; Public Facing website space;
Publishing of the Community's work;
maintained by the COP-editor (5C)
File Workspace: (5D)
http://COP.cim3.net/file/pub http://COP.cim3.net/file/pub File-sharing wokspace with people outside the community
akin to 'anonymous ftp' workspace (5E)
http://COP.cim3.net/file/resource http://COP.cim3.net/resource Library; sharing of external content collected; repository of other resources
** for reference & resources that a community does not have IPR but may re-publish (5F)
http://COP.cim3.net/file/work http://COP.cim3.net/work Workspace; project work; meeting records; repository of the community's work documents
** for work by the community, for which they have IPR (Intellectual Property Rights) on (5G)
http://COP.cim3.net/file/community http://COP.cim3.net/file/community Community related information; non-work related things (organizing a party, picnic, ...?)
** for work that the community doesn't want to openly share, or show up on search engines (5H)
http://COP.cim3.net/file/admin http://COP.cim3.net/file/admin Community & CWE admistration stuff; contact lists ... etc.; administrator access only
** for community information that requires somewhat restricted access (say, by the leadership or administrators only) (5I)
- Note: one would need to replace "COP" with the name of your community or site (like "ontolog", or "sine" or "dao", ...etc.) (A1)
- Note to Windows users who runs into trouble getting connected for uploading, the workaround is to substitute "COP.cim3.net" in the above with "COP.cim3.net:80" (this workaround resolves an issue which, we believe, is a Windows bug that plagues a lot of machines that are running Windows XP.) (ANL)
- For "Community Only" (co) CWE's: (5J)
Browse To Upload To Typical Use
------------------------------------ ------------------------------------- -------------------------------------------------------------
Portal:
http://COP.cim3.net http://COP.cim3.net/portal Community Portal; Public Facing website space;
Publishing of the Community's work;
maintained by the COP-editor (5K)
File Workspace: (5L)
http://COP.cim3.net/file/pub http://COP.cim3.net/pub File-sharing wokspace with people outside the community
akin to 'ftp' workspace for guests (5M)
http://COP.cim3.net/file/resource http://COP.cim3.net/file/resource Library; sharing of external content collected; repository of other resources
** for reference & resources that a community does not have IPR but may re-publish (5N)
http://COP.cim3.net/file/work http://COP.cim3.net/file/work Workspace; project work; meeting records; repository of the community's work documents
** for work by the community, for which they have IPR (Intellectual Property Rights) on (5O)
http://COP.cim3.net/file/community http://COP.cim3.net/file/community Community related information; non-work related things (organizing a party, picnic, ...?) (5P)
http://COP.cim3.net/file/admin http://COP.cim3.net/file/admin Community & CWE admistration stuff; contact lists ... etc.; administrator access only
** for community information that requires somewhat restricted access (say, by the leadership or administrators only) (5Q)
- Note: one would need to replace "COP" with the name of your community or site (like "ontolog", or "cosine" or "colab", ...etc.) (A2)
- Note to Windows users who runs into trouble getting connected for uploading, the workaround is to substitute "COP.cim3.net" in the above with "COP.cim3.net:80" (this workaround resolves an issue which, we believe, is a Windows bug that plagues a lot of machines that are running Windows XP.) (ANM)
Shared File Access (Upload & Download) (325)
- from the LINUX platform (ASE)
- if you run from a GUI, you would generally be able to connect to the webdav server via the file manager by connecting to, say: http://COP.cim3.net:80/work (example: I would connect to http://ontolog.cim3.net:80/work and label/bookmark that as "ontolog.cim3.net_work" and even save the password so that the webdav server is easily accessed (just like any other local directory) (ASF)
- using the example of setting up the connection to <http://ontolog.cim3.net:80/work> with the authentication pair [ ontolog-member / o-password ], this is what I would be from my ubuntu desktop, from its (GNOME nautilus in my case) File Manager: (ASG)
(drop down menu) Places | Document
(and, from the file-manager) File | Connect to Server ...
from the Connect to Server dialog box: (ASH)
Service type = WebDAV (HTTP)
Server = ontolog.cim3.net
Port = 80 (one can also leave this blank, as 80 is default)
Folder = /work
User Name = ontolog-member
[x] Add bookmark (check this box)
Bookmark name = ontolog.cim3.net_work (this is just a label, you can choose something else) (ASI)
.... then hit the [Connect] button (ASJ)
Password = o-password (this is a faked password, just shown here as an example; get yours from your CWE-Admin)
[x] Remember forever (select this radio button; again this is an example. Choose whatever is appropriate in your case.) (ASK)
.... then hit the [Connect] button (ASL)
You should now be connected to the webdav server at http://ontolog.cim3.net:80/work,
and be able to drag-and-drop files from your local machine to the Ontolog member workspace.
Anything you put there can be browsable, and downloadable via your web browser, if you point
your web browser to http://ontolog.cim3.net/file/work (and navigate from there.) (ASM)
- this also works well on KDE's Konqueror, but then one has to write "webdav://�" instead of "http://�" (--ChristophLange / 2011.10.05) (AT5)
- in general, "http://...", "webdav://�", "dav://�" or "dav:�" could be alternative syntax as may be required on different platforms (AT6)
- [ppy/2014.06.24] as another example, on the CentOS / Fedora / RHEL File Browser, one can just point to, say: dav://ontolog.cim3.net/resource provide the authentication, and get connected to the webdav server. (C4G)
- working from the shell/command-line, you may use cadaver for your WebDAV file transfer. (45)
Usage: cadaver [OPTIONS] http://hostname[:port]/path
Port defaults to 80, path defaults to '/'
Options:
-e, --expect100 Enable sending of `Expect: 100-continue' header.
*** Warning: For Apache servers, use only with version 1.3.9 and later.
-t, --tolerant Allow cd/open into non-WebDAV enabled collection.
-V, --version Display version information.
-h, --help Display this help message. (5S)
Command Reference:
ls [path]
List contents of current [or other] collection
cd path
Change to specified collection
pwd Display name of current collection
put local [remote]
Upload local file
get remote [local]
Download remote resource (ANX)
- for example: uploading to the ONTOLOG shared-file "file/work" workspace (6U)
$ cadaver http://ontolog.cim3.net/work (5T)
after logging in: try ... (AQU)
dav:/work/> ls <--[ list remote webdav server directory content ]
dav:/work/> lls <--[ list local directory content ]
dav:/work/> ? <--[ list available webdav commands ]
dav:/work/> cd tmp <--[ change directory to ../work/tmp/ ]
dav:/work/tmp/> get {filename} <--[ download a file ]
dav:/work/tmp/> put {filename} <--[ upload a file ]
dav:/work/tmp/> move {filename-1} {filename-1a} <--[ change filename ]
dav:/work/> cd .. <--[ change directory - up one level ]
dav:/work/> quit <--[ logout ] (AQV)
- ref the above mapping, "../work" rather than "../file/work" is used for connecting to the webdav server), since COP-"ontolog" is an "open" CWE. (6V)
- files uploaded to this directory will be browsable at the url: http://ontolog.cim3.net/file/work (5U)
- Here is an easy way for uploading single or multiple files (but no directories): ... (--ChristophLange / 2012.02.08) (AT9)
$ curl -T FILENAME -u USERNAME:PASSWORD http://interop.cim3.net/file/work/{directory}/ (ATA)
The trailing slash is mandatory. See the curl manpage for details. (ATB)
- from a MAC (6C)
- In the Finder, choose Connect To Server from the Go menu, type the address of the server in the Address field (like "http://COP.cim3.net/work/" for 'open' cwe's, or, "http://COP.cim3.net/file/work/" for 'community only' cwe's) , and click Connect. Enter the user name and password when prompted (like "COP-member" and "***"). (***Obtain the password from your CWE Administrator if you don't have it.) (6D)
- refer to "Connect to Server command to access a WebDAV server" in Help if necessary. (6P)
- Community Comments: (6R)
- "The WebDAV connection is not very persistent from my OSX, Panther environment. So I'm using a DAV client called Goliath 1.0. This works well." --Ken Fields / dao-forum / 2004.01.30 (6S)
- update: a colleague and I were trying to "connect to server" with the native Mac OS connectivity utility ("Connect to Server" on Mac OSX 10.5.6) and was not successful at it (the connection was made, but transfers seemed problematic.) We then downloaded Goliath v1.0.1 from http://www.webdav.org/goliath/installs/Goliath1_0_1.dmg.gz (the "here" under the Mac OS X section at: http://www.webdav.org/goliath/#download page), installed and then ran it. Connectivity and functioning worked great. We tested: upload, download, create file, duplicate file, delete file, create folder, delete folder ... and they all worked. (--PeterYim / 2009.03.08) (AOZ)
- Cyberduck works great too! I just downloaded and installed cyberduck v4.0.2 and installed it on my MacBook running OS X v10.6.7 (--PeterYim/2011.05.03) (ASD)
- I was able to natively use "connect to server" (sropdown menu "Go|connect to server" or "Command-K") on OS X Maverick and successfully connect to "http://ontolog.cim3.net/work" (after providing the access credentials) (--PeterYim / 2014.06.24) (C4J)
- from WINDOWS, use the following as an example (46)
- this is an example for someone trying to setup WebDAV access to upload to the "work" directory, which will be browser accessible at "http://COP.cim3.net/file/work/" from a Windows machine (47)
- Note: replace "COP" with the name of your community or site (like "ontolog", or "iaoa" or "colab", ...etc.) (A3)
- connecting from Windows 2000 (AT7)
To allow drag-and-drop access to the file workspace from Windows 2000 environment, do the following: (48)
1. work from your file explorer (77)
2. select Tools | Map Network Drive ... (78)
3. click on the Create shortcut to a Web Folder or FTP site link, and then go through the ensuing wizard (79)
4. Enter location as: "http://COP.cim3.net:80/work/" or "http://COP.cim3.net:80/file/work/" (respectively, depending on whether you are in an "open", or "community only" CWE) (7A)
4a. the additon of the ":80" to the network address helps resolve a possible windows bug. (ref: below) (ANJ)
5. Enter: UserName=" *** "; "Password=" *** " (without the " ") (contact your CWE Administrator to obtain the password) (7B)
6. Check off "Save this Password on your password list" (7C)
7. I'd name this location as "COP.cim3.net_work" (you can call it whatever you like, as long it will be obvious to you in future use) (49)
- example: "colab.cim3.net_work" ... or ... "cosine.cim3.net_work" (AI1)
8. Note that this exercise uses the "community" workspace as an example (it's simpler because it is symmetric -- in the sense that it requires a password for both download and upload). For open cwe's, some workspaces are not symmetric in its authentication requirements. Therefore, please make sure you refer to the URL Mapping table above before entering your webdav server location. (15Z)
This will establish WebDAV access to the file sharing workspace. You may now drag-and-drop files from your explorer to the WebDAV server (and vice versa). (4A)
- From Windows XP, do the following: (AHZ)
Example: setting up WebDAV connectivity to the COLAB /file/work workspace (noting that COLAB is an 'open' cwe) (AIC)
Right click on "Start" | select "Explore" | Tools | Map Network Drive ... | Sign up for online storage or connect to a network server | next | Choose another network location | next | enter:"http://colab.cim3.net:80/work/" | next | enter username:"colab-member" and password:"*****" (optionally) check the "save password" box | name the location:"colab.cim3.net_work" | next | finish | you may be prompted to enter the username and password again (same as above) and the option to save the password (AI9)
4a. the additon of the ":80" to the network address helps resolve a possible windows bug. (ref: below) (ANK)
[OBSOLETE, hopefully, now that we have a workaround] ... alternatively (this is where windows run into a bug), it may force a default username, if you see that do a: | cancel | from network location window, click next again | reenter username/password | it may say error, but ignore | repeat the same cancel/reenter/ignore cycle a few times | finish (either you got in ... or give up and use something other than a Windows solution. (AIB)
- Connecting from Windows Vista or Windows 7 (AT8)
- For Windows Vista or Windows 7 users, it is obvious from Googling the web, that there are a lot of issues with establishing WebDAV connectivity natively on Windows Vista so far. We have received users reporting that they have been successful establishing their WebDAV connection using DataFreeway by EngInSite (v2.0.7 build 224, as well as v2.8.4 build 233). Windows Vista users are encouraged to try using DataFreeway as their WebDAV client, until they (or Microsoft) can resolve the issues Vista or Win7 has with WebDAV. See below about where you can get these free software: - http://community.cim3.net/cgi-bin/wiki.pl?FileWorkspaceAccess#nidAO1 ) --ppy/2008.07.28 (AOW)
- I was able to successfully make webdav connections using the Windows version of Cyberduck v4.5 (14910) too! (--ppy/2014.07.24) (C4K)
- ref the above example, as of this post, there seems to be a bug in Windows XP. About a third of the people will be able to get the connection established without a hitch. Another third will run into problems when first entering the username/password (it won't take the password); and the rest will not be able to get Windows XP to work at all. (AI0)
- for those who can't get in on the first try, what usually happens is that the system tries to force you to use the username of "COP.cim3.net\COP-member", and will then reject your password (whether you use "COP.cim3.net\COP-member" or "COP-member" as the user name). What you'll need to do is to do a "cancel" at that screen (which then puts you back onto the previous wizard screen), and then repeat the process with the authentication. You may need to do this "cancel" process several times until you actually get it to work! Good luck :-) (--ppy / 2003.01.14_10:23; ppy/2005.07.22) (4C)
- From Microsoft (MS) Technet - Article ID: 287402 v4.3 dated May 17, 2007 (-posted by PeterYim/2007.08.20) (AO3)
Do the following: (excerpt from the MS article cited above, resolution item#6) (AO8)
On Windows 2000 and Windows XP, use the Web Folders Repair utility (webfldrs.msi):
1. Start Windows Explorer.
2. On the main drive, navigate to WINNT\System32.
3. On the Tools menu, click Folder Options.
4. In the Folders Options dialog box, click the View tab.
5. Click to select the Show Hidden Files check box, and then click OK.
6. Locate the webfldrs.msi file, and then double-click it.
7. Click Reinstall.
8. Restart the computer after installation has completed (AO9)
- for those who still have problems with getting WebDAV access from WindowsXP: (7E)
- " ... I gave up on connecting with XP Pro. I went through your instructions a number of times and even did no small amount of googling. You'd think M$ would fix this. Fortunately I have DreamWeaver - (it) worked like a charm." --Matthew Schneider / 2004.02.22 (7G)
- I found that after doing a cancel (when it tried to force the "COP.cim3.net\COP-member) it would finish mapping if I deleted the last "/". When the firewall message appears (using restricted level of Zone Alarm) that says "Do you want to run DLL app as a server?", I select "no" and then complete the mapping. This technique worked three times without further problems as I completed the remaining mappings. The DLL message also pops up early in the procedure, however, answering "no" here, stops the mapping action and forces you to start again. -- Susan Turnbull 2004.04.12 (A5)
- Finally learned of a workaround for this WindowsXP problem from the wikipedia article. --PeterYim / 2006.10.28 (ANC)
- See: http://en.wikipedia.org/wiki/Webdav (AND)
- Noting, especially ... "Windows XP and the "mini redirector" : Microsoft introduced WebDAV client support in Windows 98 with a feature called "Web folders". This client was simply an extension to Windows Explorer (the desktop/file manager) and later included in Windows 2000. In Windows XP, Microsoft changed the client to the "WebDAV mini-redirector". This new client works at the filesystem level, allowing WebDAV shares to be assigned to a drive letter and used by all software. However, it is also very buggy[1]. It tries to convert HTTP URL's to UNC paths e.g http://host/path/ to \\host\path\. It also often uses Windows Domain authentication when answering HTTP basic-auth challenges. One known work-around for the first problem is to explicitly specify the port number in the URL e.g http://host:80/path/. This reportedly forces the use of the old "Web folders" client. (ANE)
- I tried that on a WindowsXP machine, and it worked beautifully: (ANF)
For the "network address" use: http://<COP>.cim3.net:80/<filepath>/ (ANG)
where: <COP> = your CWE sitename;
<filepath> = WebDAV folder you need to connect to,
e.g. work, resource, community, admin,
file/work, file/resource, etc. (ANH)
e.g. use something like: http://colab.cim3.net:80/work/
(instead of : http://colab.cim3.net/work/)
( adding the "colon 80", ... to force windows to
go use the segment of code that does work!) (ANI)
- I have also been able to successfully connect to the wevdav server via this freeware WebDAV client - DataFreeway by EngInSite (v2.0.7 build 224 was used in my case) - available for download at: http://www.enginsite.com/Download.htm#Freeware (--ppy/2007.08.03) (AO1)
- Also successfully installed BitKinex and confirmed that it (its webdav client) works properly on a Windows Vista, and a Windows 7 machine. This is freeware too. Get it at: http://www.bitkinex.com/ (--ppy/2011.09.12) (AT3)
- however, it was reported [Gary Berg-Cross / 2013.12.02] that more recent versions of BitKinex may be problematic. (C4I)
- Doubled check with BitKinex? v3.2.3 on Windows Vista and it worked ok. (--ppy/2014.07.24) (C4L)
- see some test results of various webdav clients on different platforms (dav: and davs: even) here (--vc/ppy/2014.07.24) (C4M)
- webdav-sync - a utility to keep a local directory sync'd up with a webdav directory (C3Z)
- this is first recommended by ChristophLange to the OntoIOp working group in a post to their community-only mailing list [ontoiop-wg] (C40)
[ChristophLange / 2012.10.17]: ... those who contribute to the a webdav shared-workspace and
would like to have a full local copy of it, which is always in sync with the
central one, please try http://www.re.be/webdav_sync/ as follows: (C41)
Example showing how to sync up the webdav directory at http://interop.cim3.net/file/work/OntoIOp/ with a local directory ... (C42)
java -jar path/to/webdav_sync1_1.jar -bi -u http://{username}:{password}@interop.cim3.net/file/work/OntoIOp/ -d {path/to/your/local/copy} (C43)
where: -bi means bidirectional syncing. Alternatively there is -down and -up (C44)
- webdav-sync worked great! --Oliver Kutz & PeterYim (C47)
- [PeterYim / 2012.10.19]: I have tested this on various machines running - Windows, Mac and Linux too! (C48)
- Underneath the hood, this service is supported by a WebDAV (web distributed authoring and versioning) server. To learn more about it, see: http://www.webdav.org/ (4D)