1 / 13

Foundational Objects

Foundational Objects. Areas of coverage. Technical objects Foundational objects Lessons learned from review of Use Case content Simple Study Simple Questionnaire First level extensions (Codebook content…). Technical Objects. Identification, versioning, reference, etc.

minda
Download Presentation

Foundational Objects

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Foundational Objects

  2. Areas of coverage • Technical objects • Foundational objects • Lessons learned from review of Use Case content • Simple Study • Simple Questionnaire • First level extensions (Codebook content…)

  3. Technical Objects • Identification, versioning, reference, etc. • Structures for strings • Structures for dates • Structures for controlled vocabularies • Etc.

  4. What is “Foundational” • Objects required as basic parts of more complex constructions • Concepts, universes, categories, data element/represented variable • Objects required for high level search and discovery • Citation, abstract, contents, coverage, etc.

  5. Is it foundational?(could be a candidate) • High level process metadata • Requirements for the process (inputs) • What the process entailed • Who did it • When was it done • Criteria for completion • Results (outputs) • Organization and Individual information and relationships

  6. Foundational Object Characteristics • KISS principle: Keep it simple stupid • A Foundational object should have enough content to relay full basic useful information for a simple use case • Structured to serve as a base for extension • Extension adds more detail to support more complex use cases

  7. Review of Use Cases • Discovery information for metadata AND data file • Citation • Abstract • Coverage • Temporal (reference date and related subject) • Topical (subject and keyword) • Spatial (description) • For spatial search engines (bounding box, spatial object, lowest level and geographic date) • Collection content • What things make up a study and how do they relate to each other

  8. Review of Use Cases (cont.) • Provenance • Who owns it • Where is it from • How did it change • Actors, Events, Objects • Who can access, how and when

  9. Review of Use Cases (cont.) • Simple data file • Variable • Name • Physical Location • Data type • Representation (valid and invalid-missing) • Source • Concept • Universe

  10. Review of Use Cases (cont.) • Simple questionnaire • Population • Universe • Sample (frame, methodology, management) • Question • Intent • Text • Response domain • Sequencing (simple) • Concept

  11. Simple Case: Simple Study • Description of a simple data set tying together the following content: • Data item (label, location, data type, etc.) • Basic discovery information • Universe • Concepts • Code lists

  12. Simple Case: Simple Questionnaire • Description of a simple questionnaire covering: • Simple questions (question intent, text, response) • Non-complex question flow • Information on the population responding to the questionnaire (universe, sample, weights, methodology, etc.) • Concepts

  13. First Extension:Scope of the Codebook Case • Elements most commonly used from existing profiles • CESSDA • ICPSR • IHSN • This is for the description of a simple study • First level extension from fundamental objects

More Related