• ParaDocs To-Do

This method can be used to edit profile fields that normally look un-editable in ParaDocs.

1. Make a new document type that has the same field names (or arbitrary) and is “docType Switchable”
2. Make existing “gs” doctypes “docType Switchable”
3. Give permissions to the new document type, only to groups that need to access this feature

1. Highlight document
2. Click edit profile fields button
3. Choose the document type at the top and change it to the new document type; click “change doc type”
4. Edit the fields
5. Choose the document type at the top and change it back to the document type that it originally was; click “change doc type”

UMBC has node-level security implemented. This security measure is pretty specific to UMBC and is a legacy configuration of version 2.0 of the Para-Docs product, most others have node-level security turned off.

In node-level security, a single document type may be configured and used by multiple groups, but access to a particular document by a particular group depends on where the document is placed in the document tree.

For example: UMBC has a document type called “Applications”. Nearly 50 departmental groups (plus an additional 50 departmental admin groups) use this one document type. When a document created within that document type is placed in a departmental node on the document tree, only members of a group name that matches that departmental tree node are able to find that document.

Pro: Simplified administration Con: Limited flexibility

If node level security were turned off, all “Applications” for all departments would be visible to any member of any group that has “Read” privileges on the document type “Applications”.

So, in this case, there would have to be different document types for each program. Instead of one “Applications” document type, you would need to make 50 unique document types (”Applications-EDI”, “Applications-CMSC”, etc.), and the group security for the documents would prevail regardless of where on the document tree the documents were placed. Queries, likewise, would be specific to the document type.

Imaging would pick the document type for the department when doing data-entry and importing, but then not have to further decide where on the tree the document was placed, instead taking the default location for that department’s document type.

Pro: Greater flexibility Con: Greater administration

Conversion to the newer ParaDocs system will replicate the existing configuration; however, after successful completion, there is an opportunity to further administer the system to enable the elimination of node-level security.

In deployments where there is a large quantity of similar documents and growth is continuous, the document tree is often very flat and little used; in this case, queries are used for the vast majority of retrievals since retrieval via the document tree will typically bring in document lists with thousands of records.

In small Para-Docs implementations (e.g. small office use), or in implementations where the system is put in place to manage or publish a fixed list of documents (e.g. ISO 9000, Manuals, etc) the tree is useful for organizing documents into folders for quick browsing if the quantities are small and growth is relatively fixed.

Regardless of the case, every document-type has a default “Doc Path:” assigned in the “Manage Doctypes” Admin tool. This default location is where documents added via the Imaging workstation or the Web Explorer interface will go by default unless otherwise specified during the save operation.

Documents are individual records that make up an applicants profile. Workflow is a single action instance(ex: applying to grad school) linking many documents of an applicant.

There can be many documents under one user, there can be many workflows under one user. Two seperate workflows can link to the same document, yet there is still only one copy of that document. One document can belong to many workflows.

The entire Paradocs system is setup on the foundation of related data as is widely published and practiced. Documents are only contained once in the database to minimize duplication of data that is not needed.

“Samba is a free software implementation of Microsoft’s networking system...Samba runs on most Unix and Unix-like systems...The name samba comes from inserting two vowels into the name of the standard protocol used by the Microsoft Windows network file system, “SMB” (server message block).”
http://en.wikipedia.org/wiki/SAMBA

Samba drives are used in the ParaDocs implementation for many uses. They appear to windows machines as network drives / resources. Examples are:

• The Scanning stations are connected to the paradocs server via samba shared drives. The documents are uploaded to a directory in \\gsdocs.umbc.edu. Type that address into any windows address bar on the scanners and you should get some Samba shared directories. It may require a username and password to get in. See user and password settings below.
• The Collegenet import drive (Y: drive ussually). Y: drive has been mapped to the samba share \\gsdocs.umbc.edu\cnetimport . See Collegenet Import for more information.

Below is the linux shell code for setting up a user on samba. The line numbers and comments after the ; can be ignored.

adduser Emguest ;added user to linux
passwd Emguest ;set users linux password
which smbpasswd
smbpasswd -a Emguest ;add user to samba and set password
cd /etc/samba/
nano smb.conf ;add above user to shares (remember to set 'write' and 'valid' tags) in this configuration file
/etc/init.d/smb restart ;restart samba service
history ;show what you just did

The following code comes from when samba was acting up and not giving access to custom made shares on custom directories. It is a modified version of the /etc/init.d/smb start functionality. Maybe samba did not run correctly under the ‘daemon’ shell command. Maybe samba does not run under the correct user privelages when run by /etc/init.d/smb

. /etc/init.d/functions
unset TMPDIR
. /etc/sysconfig/network
. /etc/sysconfig/samba
smbd -d2 -i ; -d can be set higher to get more log/debug info
nmbd -d2 -i

A lesson learned is that linux accounts and samba accounts are seperate accounts. You must verify that both are setup before trying to login to a samba share remotely. See below for example.

sudo smbpasswd -a nyeates1