...
| Gliffy Diagram |
|---|
| name | Major interfaces and their interactions |
|---|
| pagePin | 17 |
|---|
|
Use Case: Simple OCFL - based implementation
| Gliffy Diagram |
|---|
| name | Simple OCFL implementation |
|---|
| pagePin | 6 |
|---|
|
...
Persistent vs Derived Application State
This diagram highlights the logical division of persistent content as well a derived state that persists across instance restarts.
| Gliffy Diagram |
|---|
| name | ocfl client with database as authoritative metadata sourcePersistent Storage |
|---|
| pagePin | 8 |
|---|
|
Use Case - Horizontally-Scaled Fedora Instances Running against a single OCFL
| Gliffy Diagram |
|---|
| name | horizontally scaled fedora |
|---|
| pagePin | 9 |
|---|
|
WIP: Persistent vs Derived Application State
...
OCFL Client with persistent database as authoritative metadata source
| Gliffy Diagram |
|---|
| name | Persistent Storageocfl client with database as authoritative metadata source |
|---|
| pagePin | 68 |
|---|
|
WIP: Fedora Session to OCFL Session Management - try to understand how Fedora Transactions (managed by FedoraSession) would map to a set of OCFL Sessions.
...
| Gliffy Diagram |
|---|
| name | Fedora to OCFL Session Mapping |
|---|
| pagePin | 5 |
|---|
|
Use Case: Simple OCFL - based implementation
| Gliffy Diagram |
|---|
| name | Simple OCFL implementation |
|---|
| pagePin | 6 |
|---|
|