You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently, we're selecting based on pq_fields_mag which are imputed in load_proquest/correspond_fieldofstudy.py. Now that we have the predicted MAG fields, we could use this for selecting on field level 0.
This query computes a table similar to pq_fields_mag:
createtablepq_fields_mag_futureasselect goid, ParentFieldOfStudyId AS FieldOfStudyId, sum(score) as score
from (
select goid, fieldofstudyid, ParentFieldOfStudyId, score
from pq_magfos
-- join parents at level 0inner join (
select childfieldofstudyid, ParentFieldOfStudyId
from crosswalk_fields
where parentlevel =0
) as crosswalk
on (pq_magfos.fieldofstudyid=crosswalk.childfieldofstudyid)
)
group by goid, parentfieldofstudyid
It could replace pq_fields_mag if we use the rank by score to replace the column position in the current table.
It would break some things: setup_linking may need to be adjusted, as well as link/topic_similarity_functions.py
The text was updated successfully, but these errors were encountered:
currently, we're selecting based on
pq_fields_mag
which are imputed inload_proquest/correspond_fieldofstudy.py
. Now that we have the predicted MAG fields, we could use this for selecting on field level 0.This query computes a table similar to
pq_fields_mag
:It could replace
pq_fields_mag
if we use the rank by score to replace the columnposition
in the current table.It would break some things:
setup_linking
may need to be adjusted, as well aslink/topic_similarity_functions.py
The text was updated successfully, but these errors were encountered: