Tables

subs

fields

• id
  • The id of the row in the database (incremented for every subscription added, all unique)
• faculty
  • The faculty members supported with the subscription
• faculty_contact
• financial_administrator
• grads
  • Grad students supported by the subscription
• labmanager
• machines
  • Computers that are supported by the subscription
• mfcf_supportinfo
• name
  • Name of the group that owns the support (ex. AI Group)
• notes
  • Other notes on the subscription
• pointofcontact
  • The person in which the group should contact for help
• printers
  • Printers covered by the subscription
• subscription_code
  • The subscription code of the subscription (All unique)
• subscription_type
  • The type of subscription (Desktop or Dedicated)
• units
  • The number of units ordered
• website
  • The website of the group (if they have one)

subs_md5

fields

Note

These fields are the same as above, they are just the md5checksum of them for the exception of id, that is the connector between the two tables. This is done so that if one person edits the subscription at the same time as someone else they wont just overwrite each other. It will make the second person to submit their edits look at what the other person has done first.

• id
• faculty
• faculty_contact
• financial_administrator
• grads
• labmanager
• machines
• mfcf_supportinfo
• name
• notes
• pointofcontact
• printers
• subscription_code
• subscription_type
• units
• website

Go Back To Research Subscriptions Main Page

-- RyanGoggin - 11 Mar 2005