Page Comparison

...

For each of the proposed use-cases, we'll discuss:

...

Building on the discussion of customization and extension use-cases, and on the sustainability and foundation presentation, we'll review:

The existing workflows /wiki/spaces/collectionspace/pages/666275647 for making contributions
Gaps or weak areas in the existing workflows and process
Facilitating cooperation and preventing duplication of effort
Variants or different classes of contributions. E.g.,
- a new procedure vs. a new template,
- UI translations,
- documentation and translations thereof
- etc.
Structure of the community repository
Guidelines for adopters of contributions (especially templates)

...

Configuration
Using the common REST APIs
data import and ETL
http://issues.collectionspace.org/browse/CSPACE-3894 (adding/removing fields to groups)
NS: enable http caching for static assets (put nginx in front as a proxy server? Build default config? Or can this be turned on / off in the app layer?)
- make sure connections are reused, etc.
- Starting point: http://wiki.collectionspace.org/display/UNRELEASED/Configuring+Caching+in+CollectionSpace (see the linked JIRA issue as well) - Aron
NS: we need to build an OAI-PMH endpoint providing at least CDWAlite, ideally oai_dc, etc.
- Where does this go? App layer queries item XML and transforms is using XSL? Then we hook OAICat up to just use those calls instead of pre-formatted XML from a DB?
Aron: Flow of check-ins with switch to git from SVN (particularly pertinent for the project team right now)
- When check-ins go from local to upstream, or through an origin repo (on a user's GitHub acct)
- How pull requests are handed - who takes care of them, who is notified about them

...

How it's working for you
What you need from it
When it's appropriate to use it, and when not
- E.g. When not appropriate: UI development work, very rapid UI turnaround of HTML/CSS changes via local loading with record.html

...

Versions Compared