(template) Training: KM / Create and maintain proactive Knowledge content

Body

Purpose

  • To provide basic instruction on the creation and maintenance of internal-use Knowledge Base (KB) content

User

  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>
  • 349513: Knowledge Base Team Drives
    • A component of the <Division> Knowledge Base (<Div> KB)

Procedure 

  1. Choose your template
  2. Add and Submit content
  3. Revise or Advise 
  4. Review 
  5. Retire

 

Notes

  • Easy-to-follow templates take the guesswork out of article format and content structure
  • Draft articles should be reviewed and published within 24 hours of submission to the KB Publisher
  • Article validity and accuracy is maintained through practical use, daily feedback, and annual currency review

 

Return to Training 

Support Guide: Knowledge article templates 

Purpose

  • The Knowledge Management process employs standard article templates that provide consistent structure (organization), predefined content (guidance), and format (appearance) for concise, professional documentation
  • The process also allows the creation and publication of content-specific templates, as required by subject-matter experts for non-standard documentation

User

  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>

Guidelines

  • Two types of article templates are used: standard and content-specific 
    • All article templates follow WCAG 2.0 accessibility guidelines
    • All article templates are produced in WYSIWYG and HTML versions

 

Standard templates

  • Standard templates are adequate for most articles. The following standard article templates are available in the editor tool under the Templates drop-down menu:
    • Use the Procedure article (service request / standard change) templateto document
      • standard/normal operating procedure supporting a service request form or standard change ticket
         
    • Use the Procedure article (application) template to document
      • analytical procedure (e.g., troubleshooting script)
      • maintenance procedure (e.g., work-around, corrective/preventive requirements, known-error)
      • standard/normal operating procedure (e.g., specific routine tasks)
      • technical procedure: (e.g., service implementation)
         
    • Use the Policy / Best Practice article template to document: 
      • statement of policy or best practices for an organization, service, process, etc.
      • high-level information and rules for consistent practices and compliance 
         
    • Use the Guide / Directory article template to document: 
      • introduction and general overview of a new product or service
      • directory of sources or links
      • advice on how to act in a given situation (e.g., scripts for dialog with an angry user)
      • recommended, but non-mandatory controls (e.g., recommendations, suggested practices)
      • established expectations (e.g., rules for interacting with co-workers)
      • checklists

 

Return to Template Guide 

Procedure article (service request/standard change) template 

Objective

  • To provide instruction on creating a new or or modifying an existing (asset)
    • (List all change types offered in a single service request form or standard change ticket)

Scope (optional)

  • (Processes, outcomes, and benefits, and the work required to produce them)
  • (Permissions, licenses, software, etc)
  • (Any specific limitation, if not universally applied)

User

  • (Target group)
  • (Document workflow [optional])

Environment

  • (Asset number): (Name of product, service, or technology as given in asset)
    • (Name of product, service, or technology as known by public user)
  • (Asset number): (Name of associated tool or server as given in asset)

Associated Request Form / Standard Change Ticket 

  • (Linked title of associated service request form)
  • (Title of TDX standard change ticket)

Procedure(s)

Create/ change/ modify/ reset/ delete (asset)

  1. (Create supporting procedure for each change type offered in form or ticket)
  2. (Provide reproducible, step-by-step instructions)
  3.  

 

Notes

  • (Provide qualifying notes, if needed)
  • Attach this procedure to the following Standard Request Form or Standard Change Ticket:

 

Return to Template Guide 

Procedure article (application) template 

Objective

  • To provide instruction/ to inform/ to correct/ to implement 

Scope (optional)

  • Describe when the procedure starts, when it finishes, and what other limitations are applied to the expected workflow
  • (Processes, outcomes, and benefits, and the work required to produce them)
  • (Permissions, licenses, software, etc.)

User

  • (Target groups)
  • (Document workflow [optional])

Environment

  • (Asset number): (Name of product, service, or technology as given in asset)
    • (Name of product, service, or technology as known by public user)
  • (Asset number): (Name of associated tool or server as given in asset)

Procedure

  1. (Provide reproducible, step-by-step instructions)
  2.  

 

Response Template (optional)

  • (Draft standard response to ticket requester that work has been completed)

 

Notes

  • (Provide qualifying notes, if needed) 
  • Add shortcuts for this procedure to the following KB sub-categories:

 

Return to Template Guide 

Policy / Best Practice article template 

Statement of Policy / Statement of Best Practice

  • (Requirement or provision that policy or best practice places on or extends to University or department)
  • (Expectations of provider)
  • (Expectations of user)

Contact

  • (Responsible party by position title, not by name)

Reason for Policy

  • (Reason why the policy exists: the benefit extended, the issue addressed) 

Entities Affected by Policy

  • (Identify roles or units affected or governed) 
  • (Exclusions)

Responsibilities

  • (Roles and responsibilities essential to the administration and/or compliance of the policy)

Definitions 

  • (Define terms that have specialized meanings in the policy)

Policy

  • Policy section (XXX)

 

Source

  • (List and link to source document)

 

Related Documents, Forms, and Tools 

  • (List and link to related standards, procedures and other internal or external documents that provide helpful, relevant information. Include links to forms or tools that are required for compliance with the policy)

 

Revision History

  • (Date): (action taken)

 

Return to Template Guide 

Guide / Directory article template 

Purpose

  • To inform/ instruct/ provide/ notify 

User

  • (List role, group, or department)

Environment

  • (Asset number): (Name of product, service, or technology as given in asset)
    • (Name of product, service, or technology as known by public user)
  • (List product, service, task, or event)

Rationale (optional)

  • (Describe the reason the information is being made known to the public user)

Guidelines/Directory

  • (Provide checklist, recommendations, information)
  • (Provide directory of links)

 

Notes

  • (Provide qualifying notes, if needed) 

 

Return to Training 

Procedure: Add internal-use category folder to the KB

Objective

  • To provide instruction for adding an internal-use category folder to the Knowledge Base

Scope

  • An Internal-use category folder offers limited viewing permissions for group procedures

User

  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>
  • 349513: Knowledge Base Team Drives
    • A component of the <Division> Knowledge Base (<Div> KB)

Procedure 

  1. Log in to the <Div> KB
  2. Click the + New Category button
  3. In the New Category window, enter the name of your category in the Name field
  4. For the Parent Category:
    • Leave the field blank to publish the new folder on the HR KB home page
    • Click the magnifying glass to publish your new folder within an existing HR category
  5. Set the Order field to your preferred placement
  6. (Optional) Click the Change Icon button to add an icon to your folder
  7. Click the Save button
    • NOTE: Public and group-based permissions will be inherited from the selected parent category. When a category is created without a parent, the category will be marked as public by default
  8. To change the viewing permissions for your new folder, click the name of the folder you just created
  9. Click the  pencil icon to edit your category folder
  10. In the Edit Category window, click the Permissions option
  11. UNCHECK the Inherent Permissions option
    • NOTE: When checked, the category will inherit its permissions from its containing category and therefore cannot be customized. When a category is in the root of the KB and is set to inherit permissions, it will be treated as a public item
  12. UNCHECK the Public option
    • NOTE: This toggles whether or not the category is visible to the public (i.e., users that are not logged in). If this is checked, this category will be public, regardless of any other settings configured on this category
  13. Under Category Permissions, click the option to Allow ONLY the associated groups below to view this category
  14. Click in the field under Add Groups and check the groups that should have access to the contents of the folder
  15. When you have made your selections, click in the white space outside the list
  16. Click the Save button

 

Return to Training 

Procedure: Add internal-use procedure article to the KB

Objective

  • To provide instruction and minimum content requirements for adding internal-use procedural content to the Knowledge Base

Scope

  • Document a procedure for <Div> staff to use in:
    • Troubleshooting or resolving an issue with your service or product
    • Resolving an issue or fulfilling a standard request form or change ticket
    • Resolving an issue or fulfilling a standard request form or change ticket

User

  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher
  • <Div> Group Manager
  • <Div> Support Staff

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>
  • 349513: Knowledge Base Team Drives
    • A component of the <Division> Knowledge Base (<Div> KB)

Procedure 

  1. In the <Div> Knowledge Base, select and open the internal-use folder for your service or group
  2. In the folder, click the + New Article button
  3. The Category field will be auto-populated with the name of the folder you selected
  4. Leave the Order field set to 1
    • Do not check the Pin Article box
  5. In the Subject field, give your article an appropriate title for the internal resolution 
    • Example: Procedure: Add course evaluation links to myMiami
  6. In the editor tool bar, click the Templates drop-down menu
  7. From the drop-down, select the appropriate procedure article template
    • Your template will be automatically loaded into the editor window
  8. Follow the directive text under each header to complete each section
  9. In the Procedure section, provide reproducible, step-by-step instructions that allow your reader to:  
    • Perform a specific routine task (standard/normal operating procedure)
    • Troubleshoot a problem (analytical procedure)
    • Take corrective/preventive action (maintenance procedure)
    • Implement a service (technical procedure)
  10. Label links descriptively, and include the correct hyperlink for each
  11. Use proper names when referring to products, applications, etc — check out the approved list! 
  12. Do not use graphics, images, tables, or content attachments, unless you know how to format to accessibility standards
  13. Leave the Summary and Tags fields blank 
  14. Click the Status field and select Submitted from the drop-down to submit your article for review and publication in the <Division> KB
    • Recommended: Ask a member of your group to read and test your procedure before submitting it for publication
    • Select Not Submitted from the drop-down if you are not ready to submit your article for publication
  15. DO NOT CHECK the Published to KB check box
  16. Leave the Next Review Date field blank
  17. In the Owner field, enter and select the name of your manager or group
  18. Check the Notify Owner on Feedback box
  19. Save! Save! Save!
  20. Notify your KB Publisher that your article is ready to be reviewed and prepped for publication

 

Notes

  • Use of images, graphics, and content attachments is strongly discouraged in all articles

 

Return to Training 

Support Guide: Knowledge Base Team Drives

Purpose

  • To provide information on using a Knowledge Base Team Drive to support Knowledge Base content
  • To provide instructions on requesting a Knowledge Base Team Drive, adding/removing members, and setting/changing access levels

User

  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher
  • Knowledge Management process owner

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>
  • 349513: Knowledge Base Team Drives
    • A component of the <Division> Knowledge Base (<Div> KB)

Rationale

  • The inclusion of inaccessible images, graphics, and diagrams; sensitive data, certificates, and content attachments in KB articles is strongly discouraged

Guidelines

  • Miami University's Knowledge Management Process offers the use of Knowledge Base Team Drives to support Knowledge Base content
  • A KB Team Drive allows you to store Knowledge-related images, certificates, diagrams, sensitive data, or inaccessible content and provide a direct, sharable link for use in any KB article
  • A KB Team Drive can provide extra security for highly sensitive information and restrict sharing to people within a group or the University
  • The KB manager can create and coordinate the use of a KB Team Drive for any KM-trained group upon request
    • The KB manager can add/remove members and set/change access levels to a KB Team Drive at the request of a KM-trained SME or Group Manager
    • Send an email to KBManager@MiamiOH.edu, include your group or service name and desired drive membership with corresponding access levels

Directory

  • Knowledge Base Team Drive: <Division>
    • A designated member of this KB Team Drive must be logged in to your Miami University account to access the contents of the drive

 

Notes

 

Return to Training 

Support Guide: Alias-identifier tags in KB articles

Purpose

  • To provide guidelines for acceptable use, format, and content of alias-identifier tags in Knowledge Base articles

Scope

  • Only trained Subject-matter Experts are permitted to create alias-identifier tags; and they must follow these guidelines
    • Tags generated by Blackboard agents, student workers, and untrained-others will be removed, as is standard KM practice
  • Alias-identifier tags will receive the same editorial scrutiny as article content
    • The KB manager uses article tags to generate TDX reports specific to types of articles and the various groups that generate, own, share, and use associated procedures
    • The KB manager will review alias-identifier tags, re-associate duplicate tags or tags that conflict with a reporting scheme, and remove inappropriate tags from articles and the system

User

  • Knowledge Base Manager
  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>

Rationale

  • An alias-identifier tag is a human-friendly or industry-familiar key description of content and can be used within acceptable creation, format, and content standards in the KB

Guidelines

General Use

  • Alias-identifier tags contain abstract keywords or terms that would not reasonably appear in the article title or content
    • Use alias-identifier tags to group articles according to associated external/industry practice or relative terminology
    • Create alias-identifier tags that allow your working group to share descriptive keywords that make sense within the scope of your work
       
  • Do not use tags to identify common misspellings of words that appear in the article title or content
    • Inappropriate tags will be re-associated when possible or removed from the system
       
  • Do not use tags to identify alternative spellings of words that appear in the article title or content
    • List alternative spellings for a product or service under the Environment header in the article; use notation (sic) to indicate unusual/alternative spelling
      • Example: voicemail, voice mail (sic), voice-mail (sic)
      • Example: OBIEE, BI
      • Example: myCourses, My Courses (sic)
         
  • Do not use tags to repeat words or terms that appear in the article title or content
    • Inappropriate tags will be removed from the article

 

Create and select tags

  • Create new alias-identifier tags within reason and in agreement with your working group
    1. To create a new tag, open your KB article editor and select the Settings tab
    2. In the Tags field, type your formatted tag and select the first corresponding tag suggestion
    3. Click the article Save button to save your new tag
       
  • Select existing alias-identifier tags whenever possible
    1. To add an existing tag, open your KB article editor and select the Settings tab
    2. In the Tags field, begin typing your tag and select the appropriate corresponding tag suggestion
    3. Click the article Save button to add your tag selection

 

Format restrictions

  • Use hyphens to create a multiple-word tag. Hyphens within tags are interpreted as spaces in search results 
    • Spaces and special characters are not supported in TDX tags
       
  • Use at least one alpha character (a-z, A-Z) in numeric tags
    • Numeric-only (0-9) tags are not supported in TDX
       
  • Do not use camel case (camelCase) or Pascal case (PascalCase) for multiple-word tags
    • This can create confusion when searching for the same term in a different format and lead to the creation of duplicate tags
       
  • Do not use tags to identify common misspellings or alternative spellings of words that appear in the article title or content
    • Inappropriate tags will be re-associated when possible or removed from the system

Examples of supported and unsupported tag naming criteria with rationale
Tag, as formatted Supported /
Not Supported		 Rationale
Brick-and-Ivy Use hyphens to create multiple-word tag
Brick&Ivy Tag cannot contain special characters
Brick and Ivy Tag cannot contain spaces
Brick-and-Ivey Tag cannot be used to identify commonly misspelled words of terms used in article
BrickAndIvy Multiple-word tag should not be created using camel case or Pascal case
P97900, 2019YE Append numeric characters with alpha characters to create numeric tags
97900, 2019 Tag cannot contain only numeric characters

 

Search tags

  • Use the pound symbol ( # ) to search for KB articles grouped by a specific tag
    • Example: To search the KB for procedure articles tagged with the alias-identifier tag, SOP
      1. In the KB, locate the search box
      2. Click the down-arrow and select Knowledge Base (lightbulb icon) from the drop-down
      3. Enter #SOP in the search field
      4. Click the magnifying glass or press the Enter/Return key to execute your search
         
  • Hyphens within tags are interpreted as spaces in search results 
    • Example: A KB search for the #Brick-and-Ivy tag will return search results for Brick and Ivy

 

Return to Training  ​​​​​

Procedure: Find my unpublished draft

Objective

  • To provide instruction on searching for an unsubmitted or submitted unpublished draft in the Knowledge Base

User

  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>
  • 349513: Knowledge Base Team Drives
    • A component of the <Division> Knowledge Base (<Div> KB)

Rationale

  • To reduce confusion among support personnel who must quickly search the KB for accurate and usable content, we have reconfigured certain TeamDynamix licenses and permissions to limit internal-user access to approved and published articles only
  • While this practice excludes all unsubmitted and submitted (unpublished) drafts from a standard search of the KB, these drafts are available to the Owner — usually the creator of the article — through a search of My Articles

Procedure

  1. Log in to the <Div> KB
  2. Click the My Articles tab in the secondary bar
  3. On the Search page, make sure that the Owner field is populated with your name
  4. From the Status drop-down, select Not Submitted 
  5. Click the Search button
    • If no results are returned for Not Submitted, change the Status drop-down selection to Submitted and try your search again
  6. Browse the resulting list for your unpublished draft

 

Return to Training 

Procedure: Revise KB article content (Owner or SME)

Objective

  • To provide instruction for revising internal-use procedural content in the Knowledge Base

Scope

  • Only the Owner or Subject-matter Expert named on an article are permitted to revise the content of that article
  • If you are not the Owner or the Subject-matter Expert of name, use comments or feedback to note changes you believe should be made

User

  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher
  • Knowledge Management process owner

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>
  • 349513: Knowledge Base Team Drives
    • A component of the <Division> Knowledge Base (<Div> KB)

Procedure 

  1. Log in to the <Div> KB and open the article you want to revise
  2. Click the Edit Article button
  3. Update the content of your article
    • Be sure to address all valid Not Helpful feedback comments
  4. Click Save
  5. Click the Settings tab
  6. DO NOT change Summary or Tags content
  7. Scroll to the bottom of the Settings page and advance the Next Review Date to the first day of the twelfth month from current review date
    • Example: If article is reviewed on 12/07/2021, advance Next Review Date to 01/01/2022
  8. Click Save and exit to the article

 

Return to Training 

Procedure: Advise possible KB article content change (Contributor, Advisor, User)

Objective

  • To provide instruction for using Comments or Feedback to note possible need for content changes in a published Knowledge article

Scope

  • An Observer or User who wants to advise a responsible party of the possible need for revising the content of a published article
    • Responsible party: Only the Owner or Subject-matter Expert named on an article are permitted to revise the content of that article

User

  • Observer (licensed TeamDynamix user, not the article Owner or Subject-matter Expert)
  • User (anyone other than the article Owner or Subject-matter Expert)

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>
  • 349513: Knowledge Base Team Drives
    • A component of the <Division> Knowledge Base (<Div> KB)

Procedure 

Observer Comment

  1. Log in to the <Div> KB and select the article
  2. Scroll to the end of the article and locate the Comments button
  3. Click the Comments button to open blank Notify and Comment fields
  4. In the Notify field, enter and select the owner's name from the drop-down
  5. In the Comment field, describe the change you think should be made to the content
    • Provide relevant content that should be added to a specific section
    • Identify the possible duplicate article; include the URL of the original article
    • Specify the correction that should be made to outdated, incomplete, or incorrect content

 

User Feedback

  1. Scroll to the end of the article and locate the box that contains the question, Was this helpful? 
  2. Follow the appropriate steps:
  • If you think that relevant content should be added to the article
  1. Click the Yes box
  2. In the resulting Comments field, provide the content that should be added
  3. Click the Submit button
    • The article owner will take it from there
       
  • If you think that the article content is outdated, incomplete, or incorrect 
  1. Click the No box
  2. In the resulting Comments field, specify the correction that should be made
  3. Click the Submit button
    • The article owner will take it from there

 

Return to Training 

Procedure: Discover and review feedback in KB articles

Objective

  • To provide instruction on reviewing and addressing feedback on unpublished and published <Division> KB articles

User

  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>
  • 349513: Knowledge Base Team Drives
    • A component of the <Division> Knowledge Base (<Div> KB)

Rationale

  • <Division> KB article Owners/Owning Group and Subject-matter Experts are responsible for feedback evaluation

Procedure

  1. Log in to the <Division> KB and click the Feedback tab in the secondary bar
  2. On the Feedback search page, follow these step to generate your list:
    1. The Owner field will be auto-populated with your name
      • Click the X next to your name to clear the filter and enter the name of a different owner
    2. From the buttons labeled Helpful, Not Helpful, and Both, select Both
    3. From the buttons labeled Addressed, Not Addressed, and Both, select Not Addressed
  3. Click the Search button to generate a list of all unaddressed feedback 
  4. Review each article marked as Helpful and address any comments left in feedback
    • Do not delete Helpful feedback
    • Click Marked Addressed
  5. Review each article marked as Unhelpful and address any comments left in feedback
    • If the comments are valid, edit the content to correct the error and click Marked Addressed
    • If the comments are not valid, contact the person who left the feedback for clarification
      • In some cases, the comment or correction may be better-applied to a different cause (or a new article!)
    • If Unhelpful feedback contains no comments, click Mark Addressed

 

Return to Training 

Procedure: Review currency of published Knowledge articles

Objective

Scope

User

  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>
  • 349513: Knowledge Base Team Drives
    • A component of the <Division> Knowledge Base (<Div> KB)

Procedure 

Create a KB currency review report in TDX

  1. Log in to the <Div> instance of TDNext
  2. Click the Tickets tab
  3. Click the Report option and select Report Folder from the drop-down
  4. Enter the name of your new folder: <Div> Knowledge
  5. Set the visibility of the folder to include everyone who will need to see the reports it will contain
  6. Click the Save button
  7. Click the Report option and select Report from the drop-down
  8. When prompted for the type of report you want to create, select Knowledge Base Report
  9. Enter the name of your report: <Div> KB Currency Review (Owner name)
  10. Enter the following description of your report: Currency review of articles with Next Review Date that falls within the next 30 calendar days. Articles must be reviewed and renewed for currency before the first of the month; expired articles will be retired to archive by default of currency review. Follow the instructions in the article, Procedure: Review currency of published Knowledge articles
  11. Under Select the columns you would like to see, click the Add button to add the following columns:
    • Column one: Select Subject from the Field drop-down
    • Column two: Select Category from the Field drop-down
    • Column three: Select Next Review Date from the Field drop-down; select Month/Year from the Display Format drop-down
  12. Under Add filtering to your report, click the Add button to add the following columns:
    • Column one: Select Next Review Date from the Column drop-down; less than or equal to from the Operator drop-down; the run date, plus, 30, day(s) from the Value(s) drop-downs
    • Column two: Select Next Review Date from the Column drop-down; less than from the Operator drop-down; the run date, minus, 1, minute(s) from the Value(s) drop-downs
    • Column three: Select Published from the Column drop-down; is true from the Operator drop-down
    • Column four: Select Owner or Owning Group from the Column drop-down; is one of from the Operator drop-down; click the magnifying glass to search for and select the person or group for the Value(s) field
  13. Click the Advanced button and enter the following filter syntax in the field provided: (1 OR 2) AND 3 AND 4
  14. Under Order your report, click the Add button to add the following Column/Direction options:
    • Order by: Select Category and Ascending from the drop-downs
    • Then by: Select Subject and Ascending from the drop-downs
  15. Under Choose a report folder, select the name of the folder you created in step 4
  16. Under Set the visibility of this report, select the option that will include everyone who will need to see the report; click the magnifying glass to search for and select additional groups, if necessary
  17. Under Email Delivery, click the Add button
  18. In the Edit Delivery Schedule window, select the following:
    • Interval: Weekly
    • on: Wednesday
    • Time: 8:00AM
    • Format: HTML
    • Recipients: Begin typing name and select from the resulting list; or click the magnifying glass to search for and select additional recipients, if necessary
    • UNCHECK the option, If the report has no results, send the report anyway 
    • Check the option, Active
    • Click the Save button to exit
  • When an article is due for currency review, TDX will generate and email a report to the recipient(s). Once the article has been reviewed and renewed for another year or retired to archive, TDX will filter the entry from the report.

 

Generate your report in TDX

  1. When you receive your report email, log in to TDNext
  2. Click the Tickets tab
  3. In the left panel, locate the category header, Knowledge Base Reports
  4. Locate and click the title of your report
    • Example: <Div> KB Currency Review (SmithThe)
  5. Click the Run Report button to produce your report
  6. Click each title (listed in the Subject column) to open and review each article in the <Div> KB
  7. Follow the appropriate procedure, below

 

Renew a current and valid article (no revisions needed)

  1. Scroll to the end of the article, and check for instances of unaddressed feedback
    • Evaluate Not Helpful feedback comments for possible revision to article content
    • Click Mark Addressed under each instance of feedback reviewed
  2. Read the article and check all links; verify asset information
  3. Click the Edit Article button
  4. Click the Settings tab
  5. Scroll to the bottom of the Settings page and advance the Next Review Date to the first day of the twelfth month from current review date*
    • Example: If article is reviewed on 12/07/2021, advance Next Review Date to 01/01/2022
  6. Click Save and exit to the article

 

Update and renew an outdated article

  1. Scroll to the end of the article, and check for instances of unaddressed feedback
    • Evaluate Not Helpful feedback comments for possible revision to article content
    • Click Mark Addressed under each instance of feedback reviewed
  2. Read the article and check all links; verify asset information
  3. Click the Edit Article button
  4. Update the content of your article
  5. Click Save
  6. Click the Settings tab
  7. DO NOT change Summary or Tags content
  8. Leave the Status field selection at Approved 
  9. Scroll to the bottom of the Settings page and advance the Next Review Date to the first day of the twelfth month from current review date*
    • Example: If article is reviewed on 12/07/2021, advance Next Review Date to 01/01/2022
  10. Click Save and exit to the article

 

Retire an invalid or obsolete article

 

Notes

 

Return to Training 

Procedure: Review unpublished or abandoned Knowledge drafts

Objective

  • To provide instruction for reviewing unpublished or abandoned Knowledge drafts that
    • have a status of Not Submitted or Submitted, but were never Published
    • were saved and abandoned with incomplete or no content 
  • To provide instruction for compliance with the Knowledge Management Best Practice: Assess unpublished or abandoned drafts 

User

  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>
  • 349513: Knowledge Base Team Drives
    • A component of the <Division> Knowledge Base (<Div> KB)

Procedure 

Complete and approve draft for publication

  1. Log in to the <Div> KB to review your draft
  2. Open your draft and click the Edit Article button 
  3. Update article content, as necessary
  4. Click Save
  5. Click the Settings tab
  6. Scroll to the bottom of the Settings page to Status
  7. Click the Status field and select Submitted from the drop-down
  8. Click Save and exit the editor
    • The KB Publisher will review your submitted article for publication

 

Reject incomplete draft

  1. Log in to the <Div> KB to review your draft
  2. Open your draft and click the Edit Article button 
  3. Click the Settings tab
  4. Scroll to the bottom of the Settings page to Status
  5. Click the Status field and select Rejected from the drop-down
  6. Click Save and exit the editor
    • The KB Publisher will delete all rejected drafts

 

Notes

  • You will receive a weekly update until the status of each draft has been revised and the article is filtered from your report
    • If you do not process your draft, the KB manager will consider the draft to be abandoned and delete the document from the KB
  • If you received a currency review report, follow this procedure on reviewing currency of published KB articles

 

Return to Training 

Procedure: Retire obsolete Knowledge articles to archive

Objective

User

  • <Division>
    • <Div> KB Contributor
    • <Div> KB Subject-matter Expert (SME) & Editor
    • <Div> KB Publisher
    • <Div> KB Owner/Owning Group

Environment

  • 55923: Knowledge Management Process
  • 56345: Knowledge Management (KM 2.0)
  • <00000>: Knowledge Base (<Div> KB)
    • MiamiOH.edu/Know<Div>
  • 349513: Knowledge Base Team Drives
    • A component of the <Division> Knowledge Base (<Div> KB)

Procedure 

  1. Log in to the <Div> KB to review your article 
  2. If the content is no longer relevant, scroll to the review box at the end of the article
    • Click No to answer the question, Was this helpful?
    • Enter the following text in the Comments box: Article moved to archive. Currency review determined that content is outdated, obsolete, or invalid. 
    • Click Submit
  3. Click the Edit Article button
  4. Click the Settings tab
  5. Scroll to the bottom of the Settings page, and change the article Status to Archived
    • If your TDX permissions do not allow you to archive your article, simply follow these instructions through Step 2, and notify the article Owner
  6. Click Save and exit 

 

Note

 

Return to Training 

 

Details

Details

Article ID: 99945
Created
Wed 3/4/20 2:05 PM
Modified
Wed 4/10/24 8:33 AM
Can you resolve this issue yourself?
Yes! This is self-service with a smile.