-
Notifications
You must be signed in to change notification settings - Fork 1
RIALTO Data Models & Profiles
RIALTO is primarily interested in Publications (articles, research output, publications, etc.), Agents (people, departments, agencies, organizations, etc.), and Grants. Each of these is represented by a data model that defines the scope of the entity and a metadata application profile that shows what information we capture about these entities for RIALTO's usage.
What is currently implemented within the phase 1 work cycle efforts is noted with an astericks (e.g. *
). What has available or possible data sources for the field or entity type are also indicated below, with available mappings if implemented. Unimplemented modeling remains for sake of using later, as it was derived from the original user stories, not the available or known data sources.
Publications are representations of articles, research outputs, datasets, etc. If feasible, there should link to manifestations of that Work (i.e. DOI).
- Current Sources: Web of Science
- Proposed / Future Sources: Profiles, MedLine, Dimensions, SDR
See the MAP & mapping here: https://docs.google.com/spreadsheets/d/1cgSsJfa9lbThlE-4bdpLZTu74zjvzXw3D1GyozrsEBc/edit#gid=0
Topics are subject areas or concepts. Works (Publications) may be associated with a Topic in our current implementation. Future implementations can have Grants, Departments, or Agents with a research area that is a Topic.
- Current Sources: Web of Science
- Proposed / Future Sources: Profiles
See the MAP & mapping here: https://docs.google.com/spreadsheets/d/1cgSsJfa9lbThlE-4bdpLZTu74zjvzXw3D1GyozrsEBc/edit#gid=160661200
Agents are some sort of actor involved in creating works or projects, or in supporting works or projects via grants or institutional support.
- Current Sources: CAP Profiles API
- Proposed / Future Sources: Stanford LDAP, ORCID, ISNI
See the MAP & mapping here: https://docs.google.com/spreadsheets/d/1cgSsJfa9lbThlE-4bdpLZTu74zjvzXw3D1GyozrsEBc/edit#gid=1733749800
- Current Sources: CAP Profiles API
- Proposed / Future Sources: ORCID, ISNI
See the MAP & mapping here: https://docs.google.com/spreadsheets/d/1cgSsJfa9lbThlE-4bdpLZTu74zjvzXw3D1GyozrsEBc/edit#gid=588004613
- Current Sources: None.
- Proposed / Future Sources: Unknown (can stand in for special ETD readers, advising, and collaboration relationships when encountered)
See the MAP & mapping here: https://docs.google.com/spreadsheets/d/1cgSsJfa9lbThlE-4bdpLZTu74zjvzXw3D1GyozrsEBc/edit#gid=2140388180
Grants are awards for some project(s) or work(s), usually attached to one or more lead agents (PIs) whether people or departments, and awarded or funded by an organization or agency.
- Current Sources: Web of Science, SERA
- Proposed / Future Sources:
See the MAP & mapping here: https://docs.google.com/spreadsheets/d/1cgSsJfa9lbThlE-4bdpLZTu74zjvzXw3D1GyozrsEBc/edit#gid=1293850766
- Organization Identifier == $.alias (string)
- RDF.type == FOAF.Agent, FOAF.Organization
- Organization URI == RIALTO organizations namespace + organization identifier
- Organization Alias == $.alias (string)
- Children == $.children (array of strings, identifiers for each child), mapped to OBO.BFO_0000051 for each child identifier as a child organization URI
- Organization Name == $.name (string), mapped to SKOS.prefLabel & RDFS.label as a Literal
- Organization Codes == $.orgCodes (array of strings), mapped to DCTERMS.identifier as a Literal
- Parent == $.parent (string, identifier for parent), mapped to OBO.BFO_0000050 for parent identifier as a parent organization URI
- Organization Types == $.type
- Based on $.type
- "DEPARTMENT": RDF.type, VIVO.Department
- "DIVISION": RDF.type, VIVO.Division
- "ROOT": RDF.type, VIVO.University (Always Stanford University)
- "SCHOOL": VIVO.School
- "SUB_DIVISION": VIVO.Division
- URI == RIALTO grant namespace +
$.spoNumber
- RDF.type ==
VIVO.Grant
- RDFS.label, SKOS.prefLabel ==
$.projectTitle
- DC.identifier =
$.spoNumber
+ normalized form of$.spoNumber
to aid entity resolution. normalization includes stripping out non-alphanumeric characters and downcasing alpha characters. - FRAPO.hasStartDate ==
$.projectStartDate
(parse out first 10 characters to get date string) - FRAPO.hasEndDate ==
$.projectEndDate
(parse out first 10 characters to get date string) - VIVO.assignedBy == run value of
$.directSponsorName
through entity resolution, create entity if no matches - VIVO.relates == get person URI using entity resolution on
$.piSunetId
or create person if no entity. construct PI role URI using rialto context roles namespace +$.spoNumber
+_
+$.piSunetId
. create node relating PI role (@type of VIVO.PrincipalInvestigatorRole) to grant URI usingVIVO.relatedBy
. relate role to PI usingOBO.RO_0000052
, and relate person back to role usingOBO.RO_0000053
. relate PI to grant using URI of person as@id
andVIVO.relatedBy
to the grant URI.
- RIALTO Wiki Homepage
- RIALTO Use Cases
- RIALTO Architecture
- RIALTO Data Models
- RIALTO Acceptance Criteria
- RIALTO Data Sources
- Demo Videos
- Neptune/λ Integration
- Core/Combine Integration
- SPARQL Proxy λ
- Derivatives λ
- Entity Resolver Service
- Rebuild Trigger Task
- Solr Setup
- Ingest Service
- Combine Data Sources
- Data Mappings
- Load Procedure
- Starting & Monitoring ETL
- Counting # of Publications
- Jena/TDB vs Blazegraph
- Vitro Ingest Options
- VIVO/Vitro Assessment
- VIVO Community Convo Notes
- Vitro vs Stand-Alone Datastore
- Provisioning a VM
- Deployment Process
- Toggle inferencing
- Check Inferencing is On
- Recompute inferences
- Toggle indexing
- Working with Vitro Solr
- Vitro Solr Samples
- Ingest via Fuseki SPARQL-over-HTTP
- Ingest via Jena ARQ
- Ingest via Jena tdbloader
- Ingest via Vitro SPARQL-over-HTTP
- Ingest via TDB Java API
- Vitro Logging
- Detecting TDB Changes