# Data Lifeboat Data Model

## Use Cases

- lifeboat creation is a carefully considered selection
- lifeboat creation is a response to an emergency situation

## Design Characteristics

- is archival-strength (definition tbd)
- is self-describing
- is useful standalone
- do not modify the image itself
- store original photo, or as close as possible
- balance completeness and portability
- balance verifiability w/ convenience
- be as private as the maker chooses
- make as locally accessible as possible (self-unpacking)
- make as accessible to external software as possible
- pack as much self-identifying information as near to the image as possible
- any change to the contents of the lifeboat should be recorded in the lifeboat

## Roles

- Flickr Member
- Where a photo originated
- Who posted a photo
- Who wrote a comment
- Lifeboat operator/builder
- Who selected the set of photos
- Lifeboat steward/safe harbour/dock
- Where the lifeboat is stored
- Lifeboat service/tool/generator
- What software created the lifeboat

### Role Responsibilities

- license
- t&s
- opp
- privacy

### Role Scenarios

- Dietrich wants a collection of flamingoes to be generated by Flickr Foundation's lifeboat service for storage on his own hard drive
- The Flemish Medieval Weapons Society wants their Flickr Collection generated by the Flickr Foundation's lifeboat service for storage in the National Library of Belgium

## Types

Primary types:
- image
- set
- lifeboat
- index/chain of lifeboats

## Type: Image

- flickrURL
- flickrID
- Is this in the lifeboat?
- Was it ever?
- Flickr properties
- (all Flickr properties)
- FlickrMember
- Flickr social/subject metadata
- (subset of Flickr info, TBD)
- Per Size
- rawbytes
- (all Flickr properties per size)
- type
- original size
- retrieval date
- checksum
- dimensions
- CID
- Lifeboat metadata
- [] LifeboatIDs

## Type: Set

- FlickrURL
- FlickrSetMetadata
- FlickrType: eg set, gallery, search
- (accompanying metadata)

## Type: Lifeboat

- Archive metadata
- id
- date created
- version
- lifeboat description (notes from the maker)
- updateFrequency (should update every x)
- immutable vs update-able
- make public when
- license expiry/decay
- content warnings
- write warning (these are my family recipes, take care)
- respect.txt (cross cultural care)
- Content metadata
- photo list
- flickr collection type (search, user, album, set, collection)
- how are the photos ordered?
- [] ids
- based on property from flickr metadata
- author specified sort order
- lifeboat authoring metadata
- how did you choose what photos to put in the lifeboat?
- what did you choose to exclude? what is referenced but not downloaded?
- Creator / lifeboat operator
- (who asked, selected the photos)
- Creator metadata
- (Different creators may see different photos)
- Generator
- (tool/svc, eg Flickr Fdn)
- Repository
- (svc, eg FF, LoC, BL)
- [] EventLog
- initial creation
- updates
- deletion
- photo-level updates

## Type: Lifeboat Index

- [] lifeboat ids

## Lifeboat contents

How we will actually "package" a lifeboat (zip/tarball/disk image), compression, etc are out of scope.

- /manifest.{tbd}
- What is in this lifeboat
- Lifeboat schema version - all global fields
- /database.{tbd}
- What is
- /photos/
- /thumbnails/
- /viewer/
- README.html
- LICENSE.html

### Global fields

- lifeboat schema version
- lifeboat software tool + version
- list of known lifeboat services (harbors? lighthouses?)

## Lifeboat Lifecycle

- Creation
- Publishing/copying
- Updates
- Deletion

## Open Questions

Are images lifeboat aware?
- what are the reasons they would need to be? any?

Should store all sizes, just original or original+thumb
- can generate alt sizes from original
- maybe store the sizes available, but not copies
- store hashes or perceptual hashes

Can a lifeboat be updated?
Can images be removed from a lifeboat?
- yes
- but

Can you fork/remix a lifeboat?

Can lifeboats be deleted?

How to prove you deleted a lifeboat or some contents within? (eg legally restricted material)
- referencing lifeboat ids and checksums

I removed some comments of no value to me when creating the lifeboats? Can choose all/no/some subjective metadata? Do you record the opt-out?

What does "archival-strength" mean?
- added section above to cover archival-strength vs casual

Can you create photo-less lifeboat?
- yes
- photo-less mode is a feature even
- manifest-only lifeboats
- could be like writing a will
- can pre-generate manifests for Flickr Commons, eg?
-

## Lifeboat Designer

- Flickr account is required, generally
- but you could come to fdn and ask
- Design flow: slow, intentional creation
- Emergency flow: fast, skip steps
- Hoover Manoover
- Archivist hug of death
- Select set
- Make manifest
- Assess permissions
- Allow downloads
- Privacy/social
- Safety level
- License type
- Report
- Check for flickr.org release valve
- Update manifest
- Notify consituent accounts
- Set timer/conditions
- Update manifest
- Register
- Publish
- Download
- Send copies to commons org(s)

## Relevant Standards/Formats

What standards, initiatives, formats exist that are relevant or useful for this work?

How do they differ?

What can be used or not, and why?