Skip to content

enarratives module

Jump to bottom
Sharon Grant edited this page Jul 15, 2024 · 36 revisions

FAQ | Q&A | ISSUES | LUTS | data cleanup | Workflows

Pending Structural Changes: Yes

What does an enarratives record represent?

A narrative is a story that informs the viewer about the associated attached records from other modules. A Narrative can represent a page of content on a website or other application outside of EMu.

  • Live Website
  • Application (mobile, rail, desktop, etc.)
  • Exhibit labels
  • Transect/Plot experimental design and statistics
  • Archived social/public media
  • A place to hang on to data where your focal piece of information is textual, e.g. a story.
  • A Narrative record WILL BE REQUIRED to have a narrative body.

Current Sub class Status

Subclassed?: Yes Joint module with NMAI

Mandatory Fields

  • A Narrative record WILL BE REQUIRED to have a narrative body.
  • NarTitle
  • NarNarrative
  • DesPurpose (Record Type)

Tab Switching:

  • Column Name: DesPurpose
  • Lookup List: Purpose
  • Tab switching: Yes

Record Types:

  • Archive - DEPRECATED
  • Exhibition Graphic - printed file readable by visitors; a label can appear on a graphic
  • Google Cultural Institute - content submitted for the Google Cultural Institute project.
  • Google Expeditions - content submitted for the Google Expeditions project
  • Interview - verbal/transcribed/oral histories; an interaction with a person; a discussion
  • Inventory - records the narrative results from an ecological survey. Should always be accompanied by collection events. eg Rapid Inventories
  • Social Media - archived narrative content of posts from Facebook/other social media platforms
  • Transcription -- Text that is on a physical item eg book plates, illustrations, exhibition graphics. If necessary qualify this with the Sub-type field.
  • Web Narrative -- Content created for inclusion in a Field Museum science website.

Record Structure:

  • Parent/Child; There are fields that allow you to make parent/child attachment but NO data is derived from them into the record itself.
  • Network; There are attachments to records of the same type but no hierarchy exists ie they are lateral attachments.

Summary String(s)

Requests and updates to the summary string should be submitted as issues and tagged enarratives. When approved they should be documented in structural changes.

Default

NarTitle + “: “ + SumSubtitle + DesPurpose + “ - “ + NarDate0(1) + “ [“ + EveEventsRef_tab(1).EveEventNumber

If EveEventsRef_tab.EveEventNumber NOT=EveEventsRef_tab.EveShortName + “: “ + EveEventsRef_tab.EveShortName + “]”

e.g.(6377) Plants Biabo Cordillera Azul, Inventory - 2000 [RI-2]
e.g. (2294) Exhibit Label - Catalog No. : 125985, Exhibition - 2015 [EX-1921.1: Old China Hall]

Other(s):

Other(s): None

STRUCTURAL CHANGES - Rationale

Reason(s) for Change Request: NMAI/FMNH Combined proposal - FMNH/NMAI

Streamline and standardise the module between institutions. Specific developments for FMNH IMLS Empowered Grant ME-249136-OMS-21.

Status

  • Version 9 - 31 July 2023: In test. Testing Notes
  • Funded - Yes (IMLS Empowered 2022-23)
  • Combined development with NMAI

Details

Functionality updates to better handle:

  • Documenting field inventories
  • Improved web narrative functionality
  • Including statistics
  • Automated handling of age consent from parties module
  • Relabeling tabs and fields for consistency
  • Recording community requested data updates and change requests. (NMAI)

STRUCTURAL CHANGES - Rationale

Reason(s) for Change Request Consolidated phase 1 & 2

Standardise the use of the module to make it more efficient and reflect consolidation of internal processes and workflows. Prepare for newer versions of EMu by not transferring bad data structures and dirty data.

Status

  • Version 5.1
  • Funded - DEPRECATED in favour of NMAI/FMNH joint proposal
  • FMNH specific customisation

Details

  • DEPRECATED

Field Museum EMu documentation repository 2021-

Clone this wiki locally