eke.committees

This product, eke.committees, provides display and RDF ingest of committee information into the EDRN Knowledge Environment (EKE). EDRN uses the EKE to make it easy to discover, share, search for, and retrieve all of EDRN’s collective knowledge, including cancers and other diseases, biomarkers, specimens, investigators, participants, studies, protocols, and-as in the case of this product-committee information.

Although intended for the EDRN public portal, it can be installed in any Plone compatible site.

This software is developed by the EDRN Informatics Center at JPL, operated by the California Institute of Technology, for NCI.

Installation

Use Buildout with the plone.recipe.zope2instance recipe.

Add eke.committees to the list of eggs to install, e.g.:
```
[buildout]
...
eggs =
    ...
    eke.committees
```
Re-run buildout, e.g. with:
```
% ./bin/buildout
```

You can skip the ZCML slug if you are going to explicitly include the package from another package’s configure.zcml file.

Changelog

What follows is a history of changes from release to release. For more details about specific issue IDs listed below, consult the issue tracker at https://oodt.jpl.nasa.gov/jira/browse/CA.

1.0.13 — Plone 4.3.9 Upgrade

CA-1592

1.0.12 - I Require More URLs!

CA-1348: Summary source URLs should be marked as required

1.0.11 — Protection

CA-1349: Summary ingest should be robust in the face of failures

1.0.10 — Visuals

Added summarizers
CA-1338: Fix tests for eke.committees

1.0.9 — I Had Some Chicken; Pass Me the FLOSS

First official release as free/libre/open source software.

1.0.8 — MOAR UPGRADES!

Made compatible with Plone 4.3.
Use z3c.autoinclude

1.0.7 — More Upgrades

Made compatible with Plone 4.2.4

1.0.6 — Upgrades

Made compatible with Plone 4.1.5.
CA-1001 - Put Group Spaces under Committees and ingest via RDF

1.0.5 — Test Support

This release includes:

Depending on just Plone the framework instead of Plone the application.

1.0.4 — Increases Resilience Rating by 30 for 60 minutes

This release boosts test resiliency.

1.0.3 — Sitting Down

This release updates the chair and co-chair of collaborative groups as committees are ingested from RDF.

1.0.2 — Let’s Collaborate!

Re-attaches members of committees of type “Collaborative Group” to any name-matching “Collaborative Group” objects (from edrnsite.collaborations) in the portal. You should re-ingest committees to do this re-attachment whenever you re-ingest sites (because the site ingest destroys People objects).
Uses the modern plone.app.testing framework.
Collaborative Groups are now hidden.

1.0.1 — Upgrade Cleanup

This release updates the GenericSetup profile to 4, and provides upgrade steps to that profile.

1.0.0 — Plone 4

This release makes eke.committees compatible with Plone 4.

0.0.0 — Unreleased

Initial release into beta. Creation of this project was spurred on by these issues:

CA-591 - Broken links on Committees pages
CA-718 - Replace manually maintained committee information with RDF ingest

Metadata

Release files for eke.committees 1.0.13

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for eke.committees 1.0.13
File	Size	Uploaded	Provenance	Actions
eke.committees-1.0.13.zip	51.1 kB	Sep 5, 2018	Without provenance	Details for eke.committees-1.0.13.zip

Release files / eke.committees-1.0.13.zip

Download URL	eke.committees-1.0.13.zip
Size	51.1 kB
Tags	Source
SHA-256 checksum How to use checksums	`bec93f0806d98ddb84ef4b44c09a25f144a9e3692de2e1ca8ec4b7685ac466d0`
BLAKE2b-256 checksum How to use checksums	`f99a6e5d0095f995d2a255235f296036adc7d2791a16e759c161e0beeace9576`
Upload date	Sep 5, 2018
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`Python-urllib/2.7`

Security for eke.committees 1.0.13

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.0.13 This release

Sep 5, 2018 1 release file No provenance

eke.committees 1.0.13