Overview
Image Repository is a centralized BTree-based image repository with keyword/tag-based browsing and filtering.
Image Repository is a simple folder that can hold thousands of images, and provides you with a user interface that lets you tag things with keywords effectively, as well as browse images by keywords (tags).
Its goal is to provide you with an easy way to have a centralized image library with thousands of images categorized by keywords, dates, etc.
It has special handling that lets you browse the keyword space like it was a collection of nested folders. Example: Browse to keyword “Carnivores”, you will get the available keywords “Cats”, “Dogs”, and the selection will narrow down, applying all the keywords you have selected on your path through the keyword space.
It comes complete with a Kupu “library”, meaning you can browse the keywords through the Kupu image insertion dialog to make it easy to locate images even in a large collection of images.
It has a tagging interface that lets you tag images with a thumbnail like view, and apply keywords to multiple images at once.
It uses whatever image type you have installed (it does need to be added as an addable type and be able to supply thumbnails like the default Plone image type, though).
Credits
Development sponsored by the Student Services of Bergen, Norway.
Created by Jarn AS in 2006.
Changelog
1.0.2 - 2011-10-06
Plone 4 compatibility for imagerepository_tagging.cpt. [tesdal]
1.0.1 - 2011-06-01
Remove getMsgId calls on display lists, it does no longer exist. [ggozad]
Fix templates imagerepository_view.pt and imagerepository_tagging.cpt. [cleberjsantos]
1.0 - 2010-07-02
Avoid hard GS setup dependency on kupu. [hannosch]
0.9 - 2009-02-12
Fix for images using blobs. [j23d]
Better tagging interface. [fschulze]
Updates for Plone 3.x. [fschulze]
Added support for PloneFlashUpload. [fschulze]
0.8 - 2008-09-17
Made that manage_ warning go away. [hannosch]
Added the (already defined) interface so things can be adapted etc. [witsch]
Fixed tests, moved skin registration to ZCML, minor fixes. [hannosch]
Set up actions via gs profile. [witsch]
Updated status message handling. [hannosch]
Images without keywords are now listed in kupu in the root of the keyword hierarchy, i.e. when first selecting a repository. [mj]
Fixed listing image keywords in Kupu where all images in the repository have the same keywords. This edgecase is always present when there is only one image. [mj]
0.7 - 2007-03-30
Added action to register the repository in Kupu. [fschulze]
Using interfaces, views and adapters in various places to make this more flexible. [fschulze]
Removed unused code. [fschulze]
Metadata
Release files for Products.ImageRepository 1.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 |
|---|---|---|---|---|
| Products.ImageRepository-1.0.2.zip | 57.1 kB | Without provenance | Details for Products.ImageRepository-1.0.2.zip |
Release files / Products.ImageRepository-1.0.2.zip
| Download URL | Products.ImageRepository-1.0.2.zip |
|---|---|
| Size | 57.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c26342d1f5ea52c6d30086de2934b8708879c84b773ebd92d1987133e4d272e
|
|
BLAKE2b-256 checksum How to use checksums |
011fc7b6f774d9b47e065a3951cc72d5c0cddf0754b965629358e7195ba81cc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.ImageRepository 1.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.