Zack WIP Journal

From Stadm
Revision as of 13:57, 3 August 2012 by Zack (talk | contribs) (→‎To Do)
Jump to navigationJump to search

Notes on current projects that are in progress

Wiki Pages

ERI Migration to D7

Unavailable modules for D7

  • BlogAPI
  • ImageFUpload
  • Image Module (different image module in core)
  • ImageAPI (in dev)
  • ImageCache
  • URLAlter
  • Trigger (user rules)
  • Views Exporter?
  • Sub-path URL Aliasing

Pages needed in new site

  • Events/News (which should also contain seminars)
  • Anual Reports
  • Research (Connected to people?)
    • ->SpotData?
    • What do we do with Awards?
  • People
  • Outreach?
    • Links broken
    • Should some of it become a 'links' page?
    • No need for Lesson Plans Dropdown
  • Administrative
    • Do we need ERI Graphics?
  • Contact
    • Can pretty much get rid of submenus
    • Mission is on front page already
  • External Links

Front Page

Made from Two Column Panel

  • Where are people located?
    • AM Module 1
    • Not really able to edit anything
  • Aaron's test module
  • Image Gallery is View Template from Image module?

Paths

  • Must export paths from URL aliases module
    • Might have to set them manually
    • In future,

Content Types

Note: Can't currently import content types on some installations. Need to figure out which module adds this option.

News ('news')

  • Doesn't seem like we need "news:" field.
  • Elements
    • Title
    • Date ('field_news_date')
    • PI ('field_news_pi')
    • URL ('field_news_url')
    • Body (doesn't seem to be a field)

People

  • Current "People" view is Aarons test module
    • People aren't in content type, so cant be exported
  • Need fields:
    • Name
    • Title
    • Department
    • Image
    • Office
    • Phone
    • Fax
    • Email
  • Integration of People and Research
    • Quicktabs
      • Compute
        • Person
        • Address
        • Sites
      • Admin
        • Person
        • Address
      • Researchers
        • Person
        • Department
          • Main
          • Sub
        • Address
        • Research
          • Research Page
            • Link to dept
            • Link to Research tagged with taxonomy person
              • Use "Custom Text" field, and add var to address of view module
          • Dept. Funding Page
    • Research Page
      • View automatically generates table of content type research

Export/Import Workflow

  • It seems like this process can be automated using "Features"
    • Still must test
  1. Export Content Type on Old Installation
  2. Import Content Type on Upgraded Installation
  3. Export View on Old Installation
  4. Import View on Upgraded Installation
  5. Export Content of Content Type on Old Installation
  6. import Content of Content Type on Upgraded Installation

Ask Aaron

  • Install Features on eri
  • Where is the panel on the home page?
    • Or is that its own module?
  • Computer Account Request Form was never used -- still form from old icess website
  • Reason we can't just upgrade directly
  • What is the difference between current eri-dev and live eri site? Which came first?

Theming

All CSS theming is fully commented in the global.css document in the eriomega theme

  • Added bg.jpg, wrapper_bg.jpg, and transparent_header.png to /var/www/vhosts/www.eri.ucsb.edu/sites/all/themes/eriomega/images/
    • For header images and background
    • Wrapper background was uploaded through eriomega theme settings
  • Hid site title slogan in "eriomega/css/global.css"
    • Unchecked site name and site slogan in eriomega -> Toggle Libraries
    • Unchecked Menu and Secondary menu also
  • moved id zone-menu-wrapper up in global.css
    • using margins
    • otherwise, header image pushes everything down
  • Had to make padding-left on #zone-content 30px to push it inside wrapper located in global.css
  • Set width and height of background in global.css to make it match up with wrapper background
    • In body
  • Disabled page title
  • Tried multiple methods of changing list styling
    • Edited global.css to make .menu and all li styling a disc
    • Created omega-menu.css and variants as well

Structure

  • Home is content type Basic Page with alias "home"
  • Mini panel on front page that displays two columns
  • Text content below that that displays links to previous site
  • Turned off Main Page Content block
    • Needed for some content -- like in ERI Links menu
    • All content should become its own page, or a block on an existing or new page
  • Footer block at bottom
    • Pushed down 50px in CSS code
  • Title on front page hidden in global.css
    • .front h1.title {}

People Quicktabs

  • Quicktabs of vocabulary "Employee Categorization"
    • Administrative Staff=term ID 6
    • Compute Staff====term ID 7
    • Research Staff====term ID 8
  • Page View = 'people'
    • Filtered by
      • Content type = Bio
    • Contextual Filters
      • Content: Has taxonomy term ID ------> Specify validation criteria -------> Categories ---------> Employee Categorization
      • ------------------------------------------------------------------------------------------------------>Filter Term Type ----> Term ID
    • path = people/%
      •  % shows that it is getting a variable passed from quicktabs equal to the term ID of the category of the employee

Forms

  • Categorized by taxonomy "Form Type"
  1. Travel
  2. Personnel
  3. Workers' Compensation Forms & Liability Information
  4. Miscellaneous Forms
  • Content type "Administrative Form" allows Title of form, body (for links to form), file and term (only one of which can be selected to avoid redundant links on the forms page)
    • File should have multiple upload option -- need new module for this
  • There are four separate views formatted the same way, which appear in the "content" region
    • Each filtered by its own term (i.e. "Travel," "Personnel," "Workers' Compensation Forms & Liability Information," and "Miscellaneous Forms")

Outreach & Education

  • Added taxonomy vocab "Outreach"
  1. Outreach
  2. Education
  3. Lesson Plan
  • Added content type "Outreach"
    • Can be used to add any type of Outreach... even education
      • If adding education, user should add body of text. If other term, a link field is incorporated into the form
  • Page "outreach" will contain view of Outreach and Education tables
    • Max number displayed in outreach view will be 20, but there is a pager that will allow user to view more.
    • Educational Components block placed under outreach block in "Outreach & Education" page
  • Migrated content from outreach on old eri site to www-eri

Lesson Plans

  • Trying to copy structure from old eri site, except want to make list more dynamic
    • How can we make the view register the term id for each new Lesson Plan as an argument?
  1. Field added for NID
  2. NID rewritten with text "http://www.eri.ucsb.edu/outreach/lesson-plans/plan/[nid]" and link "http://www.eri.ucsb.edu/outreach/lesson-plans/plan/[nid]"
  • To be displayed as submenu of Outreach & Education
    • Will list lesson plans
      • located at outreach/lesson-plans
    • These lesson plans can be clicked to take to following page of subpath outreach/lesson-plans/plan/[id]
  • If Lesson Plans view is edited, Lesson Plans menu item will be moved to bottom of main menu, and must be moved back up to it's place as a submenu of Outreach
    • This could be changed by making the menu static as a link and removing it's default menu link in the view
    • There isn't a way to set it as a submenu within the view configuration
  • New page view for "plan"
    • Unformatted list with contextual filter
      • Content: NID
        • Validation criteria checks to see if content type matches "Outreach, Educational Component, or Lesson Plan"
        • Then does a filter value format by Node ID, which checks URL argument, and gets matching Lesson Plan node
  • User must select unfiltered HTML if they want to write in HTML (but we should get a better text input module for this)

Links

  • There are three link category menus displayed in the External Links menu that contain links categorized by the same three taxonomy terms
    • Each menu link links to its own page, which displays a view of all links with that taxonomy term
    • The view contains three fields, Title, Link, and About
      • Title is not displayed (Exclude from Display) in Fields -> Title in view customization menu
      • Link field is displayed, and altered with "Rewrite results" (in Fields -> Links -> Rewrite Results) to display [title] and link to [field-link]
  • UCSB is cloned view of UC Links Page
  • ERI is its own view, but is a block rather than a page to be displayed below Main Page Content on Eri Links page
    • has its own URL, filter, title, etc.
  • Removed User Login in sidebar, and placed link to login form in administrative menu

To Do

  • Fix titles so they are displayed on all pages other than home
  • Add gallery and upload image
  • Get migrate module and get Aaron to help migrate features
    • We can later export the features for this site, but to keep this clean I'm going to bild fresh versions of the views that I tested on the other sites.
  • Full menu
  • What are we going to do with annual reports?
  • What should we do with search function?
    • As of now it just takes you to unformatted node pages
    • Should we do some styling to make them look better, or is there an easier way?
  • Need calendar module, display suite, multiple file upload module and "Shorten URLs?" -- we should also get a better text input module... how does CKEditor get integrated into content forms?

Activated Modules

  • Quicktabs ------------------------------Needed for People/Research
    • Quicktabs Style module activated, but do we need it?
  • CKEditor---------------Couldn't figure out how to use it...leaving it out for now.
  • Admin----------------------------------Testing to see if it allows rearranging items
    • You can rearrange by hiding 'weights'

Organic Groups

Uses and Advantages

  • For creating sort of mini private Drupals within a Drupal site
    • Could be used instead of our quasi-wiki platform.
    • Might be more advanced than we need
      • Researchers could have groups?
  • Can be used to control what and where each user posts
  • Can be viewable by anyone or members only
  • Can have mailing lists
  • OGUR allows special user roles within the group

Setup

Must be setup as a Group Type, not Group Content Type (unless for subgroup)

Helpful Links

Forum thread on using arguments in Views: http://drupal.org/node/357082

Retrieved from "http://wiki-stadm.eri.ucsb.edu/index.php?title=Zack_WIP_Journal&oldid=1033"