Resource Editor: Manifest - MVP

tomcrane commented 2 years ago

When the Manifest itself is selected for editing, by clicking the very top of the resource tree in Outline view, or by other means (e.g., a menu item), a component that presents UI for the immediate properties of the manifest is presented in the RHS.

This uses #67 , #68 , #72

Some properties of a Manifest require further components to edit them:

Simple Descriptive Properties

(string values, or lists of strings, or maps, or lists of pairs of maps)	property	editable here
label	#67	no
metadata	#68	no
summary	#67	no
requiredStatement	#67	no
rights	#73	no
navDate	see note 2	no

[x] label
[x] metadata
[x] summary
[x] requiredStatement
[x] rights
[x] navDate

Resource Descriptive Properties

Value is a complex structure that has a specific editing widget	property	editable here
provider	no	link tbc (Agent)
thumbnail	#94	see note 1
accompanyingCanvas	no	link tbc
placeholderCanvas	no	link tbc

[ ] provider
[x] thumbnail
[ ] accompanyingCanvas
[ ] placeholderCanvas

Technical Properties

For Manifest these are simple strings or string arrays, from configured lists	property	editable here	has further editor
viewingDirection	#73	no
behavior	#73	no

[x] viewingDirection
[x] behavior

Linking Properties

Links to external resources, have specific editor in #72	property	editable here
homepage	#72	no
rendering	#72	no
seeAlso	#72	no
service	#72	YES - see note 3
services	#72	YES - see note 3

[x] homepage
[x] rendering
[x] seeAlso
[x] service
[x] services

Structural Properties

Accessed through tree, or other app (structures is Ranges), or marking a point	property	editable here
items	no	(link tbc)
annotations	no	(link tbc)
partOf	no	link tbc
start	TBC	TBC
structures	TBC	TBC

[x] items
[ ] annotations
[ ] partOf
[ ] start
[ ] structures

Acceptance

[x] MVP: User is able to edit all the properties of a Manifest in the above table that have an issue link in the second column.

Notes

94 is reused on the painting list body - an image that might have an image service.
navDate is a plain literal XSD date string. We can just have a string field with a validator. A date picker would probably be less useful because the dates could be years (or hundreds of years) ago.
We'll need to have special editors for auth services, search services etc. TBC. For MVP version just assume all #72.