Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guides: Knowledgebase Search #154

Open
3 tasks
edwardsarah opened this issue Jan 19, 2024 · 4 comments
Open
3 tasks

Guides: Knowledgebase Search #154

edwardsarah opened this issue Jan 19, 2024 · 4 comments
Labels

Comments

@edwardsarah
Copy link
Member

edwardsarah commented Jan 19, 2024

Overview

We need to outline the requirements for searching the knowlegebase specific to the guides team so that the toolkit accurately reflects our needs.

Action Items

  • Review written requirements for knowledgebase
  • Identify any missing fields on the toolkit that the guides team needs displayed
  • Add missing fields to the requirements list in this issue below

Resources/Instructions

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 19, 2024

Requirements for BOP Team

  • Google ID - Internal
  • Title - Display
  • Description - Display
  • Slug - Internal
  • Active (T/F) - Internal
  • Practice Area - Display
  • Status - Display
  • Published (T/F) - Internal
  • Contributor(s) - Display
  • Tool - Display
  • Internal Source - Display if value provided
  • External Source - Display if value provided
  • Topic Area - Display
  • Usability Rating - Display
  • Review - Display
  • Date Submitted - Display
  • Asset Type - Display
  • Part number - Display
  • Primary Document ID - Display
  • Original URL - Display
  • Backup URL - Display

@ExperimentsInHonesty
Copy link
Member

DRAFT Requirements for Guides team:

  • Google ID - Internal
  • Title - Display
  • Description - Display
  • Slug - Internal
  • Active (T/F) - Internal
  • Practice Area - Display
  • Status - Display
  • Published (T/F) - Internal
  • Contributor(s) - Display
  • Tool - Display
  • Internal Source - Display if value provided
  • External Source - Display if value provided
  • Topic Area - Display
  • Usability Rating - Display
  • Review - Display
  • Date Submitted - Display
  • Asset Type - Display
  • Part number - Display
  • Primary Document ID - Display
  • Original URL - Display
  • Backup URL - Display

@aymarmsba
Copy link
Member

Note from BOP meeting: How would we know if there are 10 parts, especially if the person didn't link the docs? The title could be the same across the parts.

We could use a foreign key number (asset group)

@aymarmsba
Copy link
Member

aymarmsba commented Jan 21, 2024

We still need the following fields to be displayed:

  • Topic Area
  • Usability Rating
  • Review
  • Date Submitted
  • Asset Type
  • Part number
  • Primary Document ID
    do we have a live use case in a dev environment to review this?
  • Backup URL
    do we have a live use case in a dev environment to review this?
  • Internal Source
    do we have a live use case in a dev environment to review this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

3 participants