Class AnnotationSetTriageDaoImpl
java.lang.Object
ubic.gemma.persistence.service.AbstractDao<AnnotationSetTriage>
ubic.gemma.persistence.service.common.auditAndSecurity.curation.AnnotationSetTriageDaoImpl
- All Implemented Interfaces:
BaseDao<AnnotationSetTriage>, AnnotationSetTriageDao
@Repository
public class AnnotationSetTriageDaoImpl
extends AbstractDao<AnnotationSetTriage>
implements AnnotationSetTriageDao
Hibernate implementation of
AnnotationSetTriageDao.-
Field Summary
Fields inherited from class AbstractDao
log -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionCorpus-wide tally by verdict, for the triage queue's counts.findByInvestigation(Investigation investigation) Every judgement on any set attached to one investigation, most recent first — the per-dataset triage view, without loading the sets.findBySet(AnnotationSet annotationSet) Every judgement on one set, most recent first.findBySetAndJudge(AnnotationSet annotationSet, String judgedBy) The judgementjudgedByhas standing on this set, ornull.findEffectiveByInvestigationIds(Collection<Long> investigationIds) The effective ruling for each of several INVESTIGATIONS, keyed by investigation id.findEffectiveBySetIds(Collection<Long> annotationSetIds) The effective (most recent) judgement for each ofannotationSetIds.Methods inherited from class AbstractDao
countAll, create, create, find, findByProperty, findByPropertyIn, findIdByProperty, findOneByProperty, findOrCreate, getBatchSize, getElementClass, getEntityName, getIdentifierPropertyName, getSessionFactory, load, load, loadAll, loadReference, loadReference, reload, reload, remove, remove, save, save, streamAll, streamAll, streamQuery, update, update
-
Constructor Details
-
AnnotationSetTriageDaoImpl
-
-
Method Details
-
findBySetAndJudge
@Nullable public AnnotationSetTriage findBySetAndJudge(AnnotationSet annotationSet, String judgedBy) Description copied from interface:AnnotationSetTriageDaoThe judgementjudgedByhas standing on this set, ornull. This is the uniqueness key, so there is at most one.- Specified by:
findBySetAndJudgein interfaceAnnotationSetTriageDao
-
findBySet
Description copied from interface:AnnotationSetTriageDaoEvery judgement on one set, most recent first. The first element is the effective verdict.- Specified by:
findBySetin interfaceAnnotationSetTriageDao
-
findByInvestigation
Description copied from interface:AnnotationSetTriageDaoEvery judgement on any set attached to one investigation, most recent first — the per-dataset triage view, without loading the sets.- Specified by:
findByInvestigationin interfaceAnnotationSetTriageDao
-
findEffectiveBySetIds
Description copied from interface:AnnotationSetTriageDaoThe effective (most recent) judgement for each ofannotationSetIds.Batched deliberately: the effective verdict is a per-set "latest row" lookup, and doing it one set at a time turns a list query into N+1 round trips. Sets with no judgement are absent from the map rather than mapped to null, so
containsKeyanswers "has anyone ruled".- Specified by:
findEffectiveBySetIdsin interfaceAnnotationSetTriageDao
-
findEffectiveByInvestigationIds
public Map<Long, AnnotationSetTriage> findEffectiveByInvestigationIds(Collection<Long> investigationIds) Description copied from interface:AnnotationSetTriageDaoThe effective ruling for each of several INVESTIGATIONS, keyed by investigation id.Same rule as
AnnotationSetTriageDao.findEffectiveBySetIds(Collection)— newest ruling wins — applied across every annotation set the investigation owns rather than one set. Exists so a list view can ask about a page of datasets in one round-trip instead of one query per row.- Specified by:
findEffectiveByInvestigationIdsin interfaceAnnotationSetTriageDao- Returns:
- investigation id -> effective ruling; ids with no ruling are absent
-
countByVerdict
Description copied from interface:AnnotationSetTriageDaoCorpus-wide tally by verdict, for the triage queue's counts.- Specified by:
countByVerdictin interfaceAnnotationSetTriageDao
-