Guides: Knowledgebase Search

hackforla / guides

GNU General Public License v2.0

9 stars 0 forks source link

Guides: Knowledgebase Search #154

Open edwardsarah opened 5 months ago

edwardsarah commented 5 months ago

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

https://github.com/hackforla/BOP/issues/274
https://github.com/hackforla/knowledgebase/wiki/Data-Model
KB requirements
Hack for LA website projects search page https://www.hackforla.org/toolkit

ExperimentsInHonesty commented 5 months ago

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 commented 5 months ago

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 commented 5 months ago

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 commented 5 months ago

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?