||Student Engagement & Enrollment Services
||Career Management Center
||University Web Communications
||College of Education
||Housing & Residence Life|
|Ray Gata||Human Resources|
|Scott Harrison||Student Engagement & Enrollment Services
||College of Education
||Teacher Education Services
||Board of Visitors
||Center for Educational Partnerships
|Jason Phenicie||University Web Communications
|Tammie Smith||College of Health Sciences
Thursday, October 10, 2013
10:00 a.m. - 11:00 a.m.
WebComm - Departmental Liaison System
- Each department/college/unit now has a specific liaison within the Web Communications group.
- Departments should work directly with their liaison for content-related issues. This will help provide better interactions as the liaisons will become more familiar with the specific departments' needs.
- Technical support (general issues with the website) should be emailed to email@example.com so a Footprints ticket is created.
- If your issue needs to be addressed immediately and your liaison is out of the office, email firstname.lastname@example.org so an available team member can assist you.
- The liaisons list can be found in the CQ Toolkit under Resources.
Uploading Images/List Assets/Download Component
- All images should be uploaded to the DAM using the forms.
- Previously, in dialog boxes with an image dropzone, there was the capability to click and directly upload an asset. This has been disabled:
- Via click-to-upload, the asset only uploaded to that specific instance of that component and was not available to use elsewhere.
- Click-to-upload items did not consistently publish to the live website.
- Click-to-upload items could not carry metadata, making them non-comliant with accessibility standards.
- One of the click-to-upload components was the Download component. This component is being depreciated. Existing Download components will stay for now, but it is no longer available from the sidekick. As you update your pages, you should replace the Download component.
- In place of the Download component, the List Assets component should be used. If you need any assistance with this transition, contact your WebComm liaison.
Calendar Entries - Tip & Responsibility
- When entering data in the Start Date/Time and End Date/Time fields in the calendar/event component, be sure to change the focus of the form (click in a different field) after editing and before clicking "Create" or "Save." Your change is only committed to the dialog after a new field is selected.
- Departments that have completed migration should be posting their own events using their department calendar. The University Master Calendar form is only a stopgap for use by departments who have not yet migrated to the WCMS.
- Which calendar(s) events surface on is determined by which tags you place on the event. Typical uses are the organizational unit tags to make the event appear on the department(s)'s calendar and the University Master Calendar tag to make the event appear on the master calendar.
- Be sure to activate your event after creating it.
Proposed WCMS Development
- The Web Development team has received a list of development projects from the Web Communications team. The Web Team collectively reviewed the projects and the below presentation showcases what development will take place.
- All development is in the preliminary stages - updates on timelines, progress and changes will be made to the users group as the information becomes available.
- There is a possiblity that not all of the projects in the presentation will be completed this fall.
- There are three sections to the presentation
- Currently in development: These are development projects that are already in the works.
- Projects: These are larger, longer-term projects.
- Component Development/Enhancements: Development that will bring noticeable changes to the page and components.
- A question was asked about event tagging: Could there be a notification/approval process if other units tag your office in an event or new articles.
- This is something that the Web Team will discuss and explore the possibilities.
- A concern was raised about cross-browser compatibility, particularly Internet Explorer (IE). There is some functionality that works fine in other browsers, but not in IE.
- Internet Explorer continues to be a "problem child" for web developers in general.
- Microsoft continues to move further away from standards than bringing their browser into compliance.
- The Web Team attempts to fix compatibility issues as they arise. However, this is made difficult because Microsoft is always changing how it handles code, content, etc. What is fixed now may be broken tomorrow.
- The ODU website is designed for maximum compatibility with major browsers on major operating systems as well as mobile devices and browsers utilizing readers (for those with impaired vision).
- Jason noted that another Microsoft issue has come up with Word, Excel and other office documents in Internet Explorer. With the release of Office 365, which allows users to edit their "SkyDrive" files directly in the browser, rather than opening them up in the desktop application. Now, if users click on an Office file (Word, Excel, etc.) they are presented with options to Open, Save or Save As. They must now choose either Save or Save As. Open will attempt to open the document for live editing, which is not what we desire nor is our server set up to accommodate this functionality, so the user will receive an error.