...
(See App layer calls below for more details.)
in the mini-build in our-tenant-tenant.xml (or *-tenant.xml in app layer tree)
Add a new procedure in app layer by making the following changes:
- new base-...xml file
- new domain-...xml file
- edit base-relations.xml to add new record type as a relate-able record type
- Per Chris M, has an 'all' keyword for all relation types
- add xml include to *-tenant.xml
- edit the id / number pattern config file (also need to make the generator(s) in the services layer)
Add a new procedure in UI layer by making the following changes:
- 2 HTML template files
- main record page
- advanced search page
- 2 JSON config files in the UI's config folder
- main record page (...json)
- tab page (...-tab.json)
- Bundle overlay file
Fetch the UISpec after doing app layer config in order to make editing the HTML templates easier. This will show you:
- Selector names needed in the HTML template
- Message label keys needed for bundle
Message bundle overlay - could this be per-tenant for contributions?
App layer might be able to read all files in bundle folder
App layer merges all overlay files just once
- App layer init doesn't rebuild that - it could be added
Create advanced search form template for your new procedure
in addition, for authorities, need to edit js/Demands.js
per Yura, at some point you won't need to do that, app layer might be able to generate this for the UI
Logging for troubleshooting
...
- Document how to enable caching
App layer calls, tips, suggestions
Chris M. demoing UI calls with requests and results for:
loginstatus
(based on accountperms/0 call to the services - who you are currently logged in as)
composite
...
'basic' call to return full record without any other data, such as right sidebar data
unified configThe app layer's canonical documentation is in the
Unified Config documents on the project wiki
has the default patterns for generation of selectors
In app layer, could add Ant config-deploy to push deploy
Long discussion of <services-tenant-singular> in Ray's base-procedure-claim.xml app layer config file for Claims. Possible need to wildcard suffixes in relation searches in the services.
Return last template used in Core part
Could be used to template - for Concept authority UI tweaks, perhaps even for extending services like Group for purposes like research visits
UI layer tips, suggestions
Suggestion for Yura:
JavaScript file in the UI to compare template v. uispec, identify any mismatches
In UI payloads sent to the app layer
Sends all fields, except for descendants in empty nested structuresIn app layer, could add Ant config-deploy to push deploy
App layer
domain file
UI layer
change HTML template
message bundle overlay file
look in UISpec for generated full name
switch to dropdown requires change to select structure
otherwise, most fields all use the same HTML structure in templates; they just get decorated differently
there is some complexity around HTML positioning
if you're adding a bunch of fields, or moving around fields
- Need to pull more into the mini-build - test tree - to simulate local editing
Fake static uispecs in the test directory
Local JSON files
test/data directory
...
http://issues.collectionspace.org/browse/CSPACE-3763
Long discussion of <services-tenant-singular> in Ray's base-procedure-claim.xml app layer config file for Claims. Possible need to wildcard suffixes in relation searches in the services.
Add any new base procedures in app layer our-tenant-tenant.xml (or *-tenant.xml in app layer tree)
in base-relations.xml
add as a relate-able record type
has an 'all' keyword for various relation types
in app layer
new base-
new domain
edit base-relations
add xml include to *-tenant.xml
edit the id / number pattern config file (also need to make the generator(s) in the services layer)
Return last template used in Core part
Could be used to template - for Concept authority UI tweaks, perhaps even for extending services like Group for purposes like research visits
Fetch UI spec after doing app layer config
To see selector names needed for HTML template
Message label keys needed for bundle
Message bundle overlay - could this be per-tenant for contributions?
App layer might be able to read all files in bundle folder
App layer merges all overlay files just once
- App layer init doesn't rebuild that - it could be added
Create advanced search form template for your new procedure
.json file in the UI's config folder
*-tab.json
2 .json files
2 HTML templates - main, advanced search
bundle overlay file
...
- Need to pull more into the mini-build - test tree - to simulate local editing
- Chris discussing with Yura the possibility of creating generic files in the UI layer from app layer config, if they're missing
done at init time
pull out core bit, cspi-schema stuff, to make a standalone utility
...