Introduction
Install this package and get an alternative version of event view in your Plone site. Changes are minimal, just to add basic HTML 5 microdata information, taken from schema.org specification.
Microdata available in Web pages can be used from search engines, enhancing the quality of information indexed.
This package is a proper implementation of the collective.microdata.core product. Read it’s documentation for more information.
Details
Follow a list supported properties:
- name
Taken from event title
- description
Taken from the event description
- url
Taken from the event URL field
- attendees
Taken from Attendees field (raw data, not as Person elements)
- location
Taken from event location
- startDate
Taken from the start date
- endDate
Taken from the end date
- duration
Taken from the difference from end and start date
Support for folder content listing views
This package supports also collective.microdata.contentlisting but not depends on it (you have to manually install that add-on yourself).
Then you will be able to provide microdata information about events also when listing folders content.
See it’s documentation for knowing what views are supported.
Final notes
Providing microdata doesn’t ensure that search engines will use it.
Changelog
0.2 (2012-09-08)
Now requires collective.microdata.core [keul]
Moved logic to a IMicrodataVocabulary adapter [keul]
Added a dependency to isodate library, to be able to generate ISO 8601 duration format [keul]
Added support for collective.microdata.contentlisting
Plone catalog will now index the “Event URL” data inside the getRemoteUrl metadata column [keul]
Adaptation must be based on IMicrodataVocabulary, for support also non-schema.org vocabularies [keul]
0.1 (2012-07-22)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for collective.microdata.event 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.microdata.event-0.2.zip | 29.7 kB | Without provenance | Details for collective.microdata.event-0.2.zip |
Release files / collective.microdata.event-0.2.zip
| Download URL | collective.microdata.event-0.2.zip |
|---|---|
| Size | 29.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47f9cf4e3af9481a68921ec1ad6ff6f44986e1dcac6284b005b13268c4b0a7b1
|
|
BLAKE2b-256 checksum How to use checksums |
b0480753ad8e57057158798e2125d89b94b704b83bb24507fa57a8dc8a4624cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.microdata.event 0.2
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.
