Intended Audience and Contact Information
Contact | Chief Data Officer, Office of the CIO |
---|---|
Intended audience: | Internal UBC |
UDM Domain | Reporting |
Report Standard ID | DGR004 |
Definition
Workday Discovery Board Metadata is the data that needs to be collected when creating a Discovery Board in Workday.
A Discovery Board is a Workday feature allowing for ad-hoc, quick and simple reporting and analytics within the Workday application.
Purpose
The purpose of this standard is to achieve consistency in metadata elements for Discovery Boards in Workday.
This standard is to be adhered to at all times. Exceptions, if any, are listed in the Dispensation section.
Standard
All Discovery Boards are required to capture the following metadata with the prescribed rules:
Metadata | Description | Format | Requirement |
---|---|---|---|
Discovery Board Name |
The title used to refer to the Discovery Board. |
Refer to Discovery Board Name section |
Required |
Discovery Board Description |
The business need or objective for the Discovery Board, point of contact and the intended audience of the Discovery Board. |
Refer to Discovery Board Description section |
Required |
The following rules are to be used when for naming a Discovery Board:
Item | Guideline | ||||||
---|---|---|---|---|---|---|---|
Title case |
Use title case i.e., use capital letters for the principal words; do not capitalize prepositions, articles, or conjunctions. |
||||||
Length |
As much as possible, keep the length of the report name limited to allow it to be fully visible on the end users screen. |
||||||
Avoid using "Discovery Board" |
There is no need to add the word 'Discovery Board' at the end of the Discovery Board title unless there is a need to differentiate it from a business process or other Workday elements. |
||||||
Abbreviations |
Avoid using abbreviations unless it is institutionally common practice to abbreviate a word or phrase. Longer, more detailed names can be very useful in communicating the purpose of a Discovery Board to all users in different functional areas.
|
||||||
Be clear, specific and consistent |
Avoid general terms such as "Expense Dashboard V1" or "Expense Dashboard V2". Use a specific name – for this example, the name should be updated that explains the differences between V1 and V2. The report name should clearly state the purpose of the Discovery Board. Be mindful that Workday is UBC's system of record for HCM, Finance and Student data. Use a descriptive name to give the user an idea about what the Discovery Board provides. This also helps eliminate Discovery Board with the same name. Think about a consistent naming format that works for you and your team, so you can locate them quickly. Having consistency in the name would also help them appear in the Drive folder in a desirable order. |
||||||
Duplication |
Avoid duplicating the same name for a different Discover Board. Each Discovery Board must have a unique name. |
||||||
Allowed Characters |
See Allowed Characters for System Interoperability Data Standard. |
The information provided within the Discovery Board description will help the support team and any other user of the Discovery Board to quickly identify and understand what it is.
The description should be captured in the Enter a board description field located below the Discovery Board name (click for larger image).
Below are the metadata to be captured in the Enter a board description field:
Description Metadata | Definition |
---|---|
Point of Contact Name |
The name of the individual that would be able to respond to any related inquiries for the Discovery Board. |
Point of Contact Functional Unit |
The name of the functional unit the point of contact belongs to. |
Purpose |
The business need or objective of the Discovery Board i.e. why is the DB created. |
Intended Audience |
The end-users of the Discovery Board. |
Enter each detail as shown in the screenshot below (click for larger image):
Be sure to click Apply to save the entered details.
Compliance
This standard must be complied through every stage of Discovery Board development and maintenance with the exception of any dispensations (see Dispensation section).
Dispensation
None
Related Documents
None