Versions Compared

Old Version 4

changes.mady.by.user Patrick Schmitz (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Angela Spinazzè

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel3
printablefalse

...

See Short Agenda

...

Agenda: Wednesday, February 8th (Start time: 1:00pm)

...

Related Discussion and Documentation

Discussion and Process Around External Code Contribution

Code Contribution Draft Workflows/wiki/spaces/collectionspace/pages/666275647

/wiki/spaces/collectionspace/pages/666276054

/wiki/spaces/collectionspace/pages/666276095

...

9:15-11:15: Walk-through of customization and extension use-cases

Meeting notes, 9 Feb 2012 AM

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

...

We'll canvas the group to choose from among the following list of use-cases. Most of them will illustrate general principles, but each of them has distinct technical issues.

...

  1. Customize a procedure or authority

      ...

        1. Add a field to a local or domain schema (in a new tenant)
        2. Apply another schema (from a template) to your record
        3. Add validation
        4. Roles and Perms and field-level perms
        5. Rename field or authority
        6. Add a field to a repeating field group (can not be done now without replacing the whole group -- what could we do to change this in the system?)
        7. Blue sky: Fundamentally change the data model (e.g., to display information from a related record on the main panel or right panel)
      2. Build a custom procedure (e.g., Claim/NAGPRA Claim)
      3. Build a custom authority (e.g., Place)
      4. Add UI widget or capability

      ...

      1. following discussions in the pre-meeting on Tuesday)
        1. Add a boolean widget
        2. Add link/button that examines a field that is a URL (e.g., link to image in another system) and open browser window)
        3. Add link/button that talks to an external web service (e.g., sends locality info to Berkeley Mapper and draws a map; sends locality text info to a georeferencing service, gets back locality data, stores data in system)
        4. Modify/extend report invocation widget to also invoke batch processes
        5. Modify report/batch widget to display a dialog requesting parameters for invocation
        6. Integrate data from related record on page

      Related Discussion and Documentation

      ...

      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?)
      • 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
      • ...

      4:45-5:00: Wrap up, next steps

      ...

      Agenda ideas, to be inserted:

      More discussion of query or export or? for supporting things like public browsing.

      Possibilities:

      1. Use the application layer to map services into a data model for the public browser
      2. Build new services that aggregate things for common cases
      3. Use a data warehouse model that exports CSpace data to a custom DB just for the browser.

      Think about issues around media reuse sharing.

      Managing documentation for current deployments

      For sharing of experience, pain, etc.

      Integration with external systems

      Regular, automated import or export from/to another system

      Linking to DAM systems, etc. for media management.

      Fetching data, sending data, upon user invocation for specific tasks (placename resolution, mapping, query or export to genomic DBs, etc.)

      Adding constraint logic on entered values

      • In the UI vs. in the services (user entry constraints, vs. data constraints including on import)
      • Code development and maintenance in Javascript vs. Java

      Mini-build

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

      BOF (birds of a feather) sessions on specific topics

      Do we want to consider this, or should we keep discussions global with everyone?

      Specific topics might include:

      • Custom widgets, e.g., modifying structured date behavior
      • Citation authority requirements
      • Concept Authority for various authorities
      • CDWA (lite) mapping