Home Areas and Access

From UA Libraries Digital Services Planning and Documentation
Revision as of 13:40, 17 June 2016 by Jlderidder (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The Head of Metadata & Digital Services currently manages home areas, passwords, and access for library personnel to:

  1. etd01 (the ETD incoming server)
  2. libcontent (Acumen and the archive, primarily)

For directory structure and access points for the metadata librarians, see Server_support.

On libcontent, the greatest amount of space is in the /srv/ area, so that is where Uploads and Deposits and the archive are, as well as scripts and Acumen content.


/srv/UPLOADS/ contains: AUDIO, MassContent, scripts and UploadAreaDS. The ds user (digital services uploading staff) have softlinks to each of these areas in their home directory (the last one is called UploadArea). This may also be true for staff who are provided their own login, as they will be doing server work beyond simple uploads.

Other softlinks to areas in /srv include:

  1. acumen ( /srv/www/htdocs/content/)
  2. deposits (/srv/deposits/content/ -- this is where content is deposited during uploads for archiving)
  3. allDeposits (/srv/deposits/ -- this also includes EADs, crowdsourcing, ETDs, etc.)
  4. archive (/srv/archive/)

In order for both Metadata Librarians and Digital Services to work in the Acumen web area, users in both areas belong to the group "www", and permissions for content in all directories there must be set to "775", as this will allow anyone in this group to write files to those directories.

For example, this is one line of the results when typing in "ls -lai /srv/www/htdocs/content/:

drwxrwxr-x    5 jeremiah www    49 Mar 14  2014 p0001

Similarly, the archive area belongs to group "group-archive". Members of this group include the Technical Lead, Head of Metadata & Digital Services, and the Repository Manager, as access to this area needs to be restricted.

To add users and home areas, see Linux documentation, such as Useradd. When setting passwords, communicate them via phone whenever possible, as email is not secure.