The myEOL Weekly Digest is a bi-weekly newsletter that goes out to the campus every Monday and Thursday at 10 a.m. Two separate newsletters go out to the campus: one to current students and one to faculty and staff, with the content curated appropriately for each audience.
Note: Content for the newsletter is not manually curated; instead, it is automatically pulled from content entered within myEOL’s content management system (CMS). For details on how content is organized for automatic inclusion, please see the sections below.
How Content Is Pulled: Announcements
For announcements, the digest pulls based on the date the announcement was entered into myEOL. The most recent five announcements will be included in the newsletter. For those that were entered later, they can be viewed by clicking the “Read All Announcements” link.
Note: The newsletter also filters based on audience and sends out a different content to the two audiences (students and faculty/staff). Thus, if you have requested an announcement in myEOL that is marked as only visible for students, you will not see it in the employee newsletter, and vice versa.
How Content Is Pulled: Events
For events, the digest pulls based on the date of the event (not the date when the event was submitted). It takes the current date (the day the newsletter is going out – either Monday or Thursday) and finds the five events that are closest to it. It excludes events that are past the current date.
Note: The newsletter also filters based on audience and sends out a different newsletter to the two audiences (students and faculty/staff). Thus, if you have requested an event in myEOL that is marked as only visible for students, you will not see it in the employee newsletter, and vice versa.
When/How to Submit
Because the content is automatically pulled from myEOL, the content must be in myEOL as an event or announcement and published before 10 a.m. of the Monday or Thursday of the newsletter release.
To request an announcement or event, please use the following ticket link: https://nccu.teamdynamix.com/TDClient/1852/Portal/Requests/ServiceDet?ID=37098
To allow time for the publication process, please allow at least 3 business days before the desired date of publication (for events, we recommend this date be at least a day before the event itself to give viewers time to see the event).
- Monday Newsletter: If you want your announcement/event to go out with the Monday newsletter, you should submit no later than Wednesday morning of the preceding week.
- Thursday Newsletter: If you want your announcement/event to go out with the Thursday newsletter, you should submit no later than Monday morning of the same week.
The timeframes above assume that all content is provided and responses to all Web Service inquiries are prompt. If the event that we find an issue with the content or do not receive responses, we cannot guarantee publication within this timeframe. To ensure publication in time for a specific newsletter, we encourage you to submit as early as possible, make sure your content is all present and ready (see section below for details), and respond promptly to any messages from the Web Services team.
Note: One final point to keep in mind is that all events/announcements require the requestor’s approval before publication. Thus, if you do not approve the content, we cannot release the page, and it will therefore not be included in the myEOL newsletter or on myEOL’s home page.
Preparing Content
The ticket type for announcements/events has fields for all the important pieces of content needed to create an event/announcement. Thus, the first step when preparing the content is to review the ticket fields and make sure you have the content to fill them.
Images
The most common causes of delays in publication are issues with the image provided. All announcements/events require an image, and while we can work with most high-resolution images provided, we cannot use images with any text (besides a logo) in them.
Thus, please keep the following in mind when sourcing an image:
- Do not include any text (besides a logo) in the image.
- Images must be larger than 1000x590 pixels. Images larger than 3000x1770 pixels will be resized.
- 1 MB limit.
- Allowed types: png gif jpg jpeg (we recommend jpg).
- Must have permissions for posting to web.
As a source for images, we recommend using our Photoshelter (https://nccu.photoshelter.com/galleries), as these images will guarantee that you have the appropriate permissions and have access to high-quality images of the appropriate size.
If you do not provide an image, the Web Services team will assist you in finding one. However, please note that this will slow down the publication process, so if you do not submit an image, please be prepared to allow for a longer turnaround time.
Links
Another common area for issues to occur involves links. If you are submitting a virtual event request, you must include a link to either register for the event or a link to the event itself (e.g., on Zoom or WebEx).
Note: if you need a registration form for an unpaid event, our team can help you with this, but it may increase the time for publication. If you have a paid event, we are also able to assist, but this can take significant time if this is the first time your department has arranged for paid events with us. We encourage all paid events to speak to us several months in advance to discuss the options available.
Audiences
As noted above, the audience section controls which newsletter your event/announcement is included in, so it’s very important that you select the correct audience to get the result you intend.
If you only want it to go out to students, just select “Students.” If you only want it to go out to faculty/staff, just select “Employees. For both employees and students (but not individuals outside of the campus community), select “Students & Employees.”
If you want this event/announcement to be available to everyone, select “Public” and “Students & Employees.” If you don’t select “Students & Employees,” Web Services will still select this option for you when preparing the content, but to avoid unintentional oversight, it’s best to check it.