The Data Entry Problem
The Data Entry Problem
Here's a quick run-down of some of the related data entry issues, and recommended work-arounds.
Modern Event creation/edit screens only support a single default “Category”
Most of us have a hierarchy of metadata we’d like to be able to sort, filter, and group by. It is super easy to create additional metadata columns, but you can only use these fields in Classic views.
In my idealized scenario, I’ve segregated major categories of events with separate communication sites for each. This allows you to maintain News articles and calendars that are separate and still retain the single native “Category” calendar field for “sub-categories” which I’ve shown examples of here.
Official Company Events
- Official Events
- Important Deadlines
- Training Opportunities
- Sponsored Events
- Office Closure Dates
Flag any Company Event as Important
Ability to highlight any event as important to deliver a list of future important events. Requires 2 metadata columns.
- Highlight as Important
- Importance Expiration Date
Notices and Alerts
- Maintenance Windows
- Operational Alerts
- Facility Alerts
- Equipment Alerts
- Change Management Reminders
- Team/Staff Reassignments
- New Hires
- Staff Exits
- Employment Anniversaries
- Personal Announcements
Highlighting an event as an important one
All events are not created equally. Some are important and need to be called-out so people pay more attention to them. This is a very critical requirement for critical operational and key business communication.
One of my previous posts outlines how to highlight important news articles using two meta-columns. We’ll use this same approach for highlighting important Calendar Events.
The only bump is that Contributors must be in a Classic event view when working with the highlight fields. The Modern event interface doesn’t reveal custom columns on the create/edit form.
This issue is eliminated by adding a button near all event views, to take the visitor to a monthly view, and then train your contributors to create their events here. Specs for the additional Metadata fields this approach requires are at the end of this article.
Specs for the additional Metadata fields this approach requires are at the end of this article.