Web Services

Web Procedures

Web Processes are completed by two groups within University Relations: Web Content and Web Services.

Web Content, under the direction of Elaine Keough, oversees all web content including generation of all news, site specific content, university communications, UML Today, content updates and initial contact with university colleges, departments and administrative units to create new or update/edit existing web sites, social media, blogs, photo galleries, university calendar, maintenance of top level pages, project management for e-commerce, marketing language, approval of daily tasks.

Web Services, under the direction of Gerry Nelson, manages the enterprise web applications including both web content management systems (Serena Collage, SDL Tridion), Lyris List Manager, WebTrends Reporting, University Wiki, and University Blogs.  Web Services oversees web functionality and custom web applications programming, forms building, page design, layout and graphics, interactive design, and user interface design for entire online university presence. Also responsible for design and layout and building of internal presentations and e-communications (eVites, eNewsletters).  

Web requests will soon be routed through a new help system.  The system is currently being tested.  This help system will provide a means of communication and tracking of requests, and also provide a knowledge base for the use of our enterprise systems, and common end user tasks.

Types of web requests:

Need password/access to site:

  1. Web Content/Services receives request from client. Direct client to online ticket submission form.
  2. Ticket assigned to Web Content for verification and then reassigned to Web Services for access to Collage/Tridion. 
  3. Web Services checks/resets the permissions.
  4. Web Services/Ticket system emails client with information.

Request Alias:

  1. Web Content/Services receives request from client. Direct client to online ticket submission form.
  2. Determine if alias is temporary.  If so create tinyuml and close ticket. (step 6)
  3. Recommendation made to client for appropriate alias. 
  4. Ticket sent to Web Services with existing URL and requested alias.
  5. Web Services creates alias
  6. Web Services closes help ticket which alerts client that alias is complete. 

Bad Links:

  1. Web Content/Services receives request from client. Direct client to online ticket submission form.
  2. Web Content fixes repairs bad link(s).
  3. Web Content closes help ticket which alerts client that link has been repaired.

Have site listed in the Directory:

  1. Web Content/Services receives request from client. Direct client to online ticket submission form.
  2. Web Content checks to see if site is already listed.
  3. If site is not listed, Web Content adds the site to the list under the appropriate letter(s).
  4. Web Content alerts client that change has been made. Web Content closes help ticket which alerts client that directory listing is complete.

Have changes made to the People Search Directory:

Update Existing Site:

Sites in Collage can be updated.

Tridion training is held twice a week. For the latest training, visit xxx. 

Redesign existing site:

Due to the transition to Tridion, we are not redesigning any existing sites in Collage.

Create new site in CMS:

  • Import
  • Build
  • Graphics/Photographs
  • Format
  • Test
  1. Web Content takes request from client.
  2. Web Content initiates project by contacting Web Services.
  3. A web content person is assigned.
  4. Web Content meets with the client to gather general information and photographs.
  5. The client will sign up for training in SDL Tridion - to learn how to work within the workflow and also edit/add content.
  6. Alias requests sent to Web Services if necessary.
  7. Images/photos chosen for creative areas and body content. 
  8. Web Content works with the client to customize navigation, develop site structure and designate workflow.
  9. Approval of staging site via workflow/email or meeting.
  10. Special applications are created by Web Services if needed.
  11. Content will be generated by the client and/or web content or other contributor and approved via workflow.
  12. Site is populated within Tridion. Content Contributor alerts content team via workflow.
  13. Web Services builds navigation and site structure.
  14. When design and content are completed, content approves deployment to a staging server and contacts the client via workflow to review the site.
  15. Site is deployed to the staging server.
  16. Review/test the site on the staging server with multiple browsers and operating systems.
  17. Site deployed to live UML server.

Create Evite:

  1. Web Content takes request from client.
  2. Senior web editor is assigned, reviews request and obtains approval by vice chancellor for university relations for evite.
  3. Senior web editor determines “send” lists (Internal, external, faculty/staff/student and breakdown, if any).
  4. Senior web editor writes/edits evite.
  5. Senior web editor obtains approval from client and sign off on content.
  6. Client provides images/photos chosen for creative areas and body content. (Note Web Services has final review and selection of imagery graphics according to university standards and branding.)
  7. Evite built by Web Services and test sent to client and Web Content.
  8. Final approval and schedule to send.

Forms Creation

There are three forms that we offer:
  1. Email submission
  2. Submission to database
  3. Ecommerce form

For each form request send a ticket to Web Services in Word or similar with fields and information identified:
  • Type of form – Email, Database, Ecommerce
  • Introductory text, if needed
  • Fields needed (This includes submitter's contact info, form questions, etc.)
  • Fields required to successfully submit the form, application, or survey
  • Specify e-mail address(es) for those needing to be notified of successful submissions with a copy of the filled out form.
  • Automated “Thank you” text and/or confirmation email after form is filled out, if needed.

Procedure to Build Forms:

  • Forms built by Web Services
  • Linked to email/DB by Web Services
  • Access to DB/Reporting by Web Services.
  • Test
  • Deploy

Blog Request:

  1. Web Content/Web Services takes request from client.
  2. Client instructed to log into http://blog.uml.edu/ to initiate account. Receives error message.
  3. Client informs Web Services of account creation.
  4. Web Services sets up blog and designs custom blog banner.
  5. Client alerted that blog is ready.

Have event/site included in “Spotlight:” 

  1. Web Content takes request from client.
  2. Web Content reviews request and posts in “Spotlight” if approved.

Have event/site included in “Features:” 

  1. Web Content takes request from client.
  2. Summary and graphics of feature are provided by client.
  3. Web Content reviews request, if approved determines what feature landing page to display feature.
  4. Web Content writes/edits content and sends feature to Web Services.
  5. Web Services creates feature and posts on date requested.

Have event included in calendar of events:

Adding keywords to UMass Lowell search (powered by Google):

  1. Web Content/Services receives request from client. Direct client to online ticket submission form.
  2. Web Content reviews request for approval.
  3. Web Content forwards to Web Services for implementation.
  4. Ticket is closed to alert client.