Open arowla opened 10 years ago
What is unique about awards as opposed to PRESOLs/COMBINEs? Does one "just" need to modify process_notice()
and associated functions to extract fields from the JSON representations of awards
I think the most important distinctions are the recipient information, award amount(s), and award id. Like mentioned in #16 it allows for direct comparison with USASpending/FPDS expenditures.
One of the issues with award ids is that you can have multiple ids if you have multiple recipients, and instead of delimiting them, they sometimes just use a weird "range" notation. For instance,
HHSM-500-2007-00014I-00028I
(as seen in https://www.fbo.gov/index?s=opportunity&mode=form&tab=core&id=e30fa27ef8f8dd65067d579645809c52&_cview=0)
Really means:
HHSM-500-2007-00014I HHSM-500-2007-00015I HHSM-500-2007-00016I HHSM-500-2007-00017I HHSM-500-2007-00018I ... HHSM-500-2007-00028I
So it's a bit weird because agencies don't uniformly create award ids/piids in the same way. They are essentially namespaced by agency and sometimes program office. It would be nice if there were a way to have the input be comma delimited, otherwise it's a bit tricky to untangle.
Isn't it also possible to have multiple awards notices per solicitation? (Haven't had the time to research this yet...)
Probably? I don't know for sure.
I suggest making the awards a separate REST resource (/awards) -- see SBIR.gov . Then allow each solicitation support having multiple award notices.
For SBIRs, each solicitation / topic can (and usually does) have 3 selectees for Phase 1. I know that many awards also have primary contractors and subs -- not sure if that is just a single award notice or multiple (probably just single).
We still need to figure out how we are going to treat awards. My initial thought is to have them be a different doc type in Elasticsearch.
But this will likely allow us to do some cool things, such as link awards to usaspending.gov. (See #16.)