data.gov feature list

[jbrown-xentity]

Purpose

We want to have a complete feature list of data.gov (categorized via MuSCoW: Must, Should, Could, Would), but we're not sure how to do that.

Given above has grown over the last decade, conducting research, code review, and documentation is needed to provide factual knowledge on future steps.

2 days of effort has been allocated and once compete, findings will be demonstrated and specific future actions will be decided.

Acceptance Criteria

[ACs should be clearly demo-able/verifiable whenever possible. Try specifying them using BDD.]

• GIVEN an audit is complete
  WHEN 2 days of effort expires
  THEN a detailed spreadsheet is given
  AND a discussion is had on future data.gov tickets/epics

Background

Came out of discussion from harvesting discussion

Sketch

The spreadsheet should contain Feature, why (if available/applicable), complexity (t-shirt size), category (UI, harvesting, SEO, search, etc), sub-category

[jbrown-xentity]

Feature List on data.gov drive

[jbrown-xentity]

I left some more comments, notes, and items around the Open Data Act on the Feature List. We should review this during a pairing session to answer questions and finalize on this for planning future epics.

[jbrown-xentity]

After review with @nickumia-reisys and his work on #4089 , we have merged this where each feature is listed with it's corresponding law/memorandum requirements. See the Feature List on data.gov drive for latest information. This can be considered done, with review occurring with team during sprint review after discussions.

[nickumia-reisys]

This is a beautiful ticket 🥲

[nickumia-reisys]

Related to

• Collate Data.gov mission/vision #4354