XMLSource
A simple transmogrifier blueprint to read xml files of the form
<container>
<item>
<field1>value</field1>
<field2>value</field2>
...
</item>
...
</container>
Example
The following example uses funnelweb and ploneremote to upload content in an xml file from the commandline
First create a custom pipeline.cfg
[transmogrifier]
pipeline =
xmlsource
ploneupload
ploneupdate
[xmlsource]
blueprint = transmogrify.xmlsource
xmlfile = items.xml
pathtag = field1
itemtag = item
type = MyCustomType
[ploneupload]
blueprint = transmogrify.ploneremote.remoteconstructor
target = http://admin:admin@localhost/Plone/mycontent
[ploneupdate]
blueprint = transmogrify.ploneremote.remoteschemaupdater
target = ${ploneupload:target}
Now install funnelweb using a buildout.cfg
[buildout] parts = convertxml [convertxml] recipe = funnelweb pipeline=wynhotels.cfg eggs = transmogrify.xmlsource
bootstrap
$> easy_install zc.buildout $> buildout init $> bin/buildout
and now run your custom converter
$> bin/convertxml
The converter parses the xml and uploads to plone via xmlrpc. or construct your own pipeline to transform the content into whatever or whereever.
Metadata
Release files for transmogrify.xmlsource 1.0
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 |
|---|---|---|---|---|
| transmogrify.xmlsource-1.0.zip | 6.2 kB | Without provenance | Details for transmogrify.xmlsource-1.0.zip |
Release files / transmogrify.xmlsource-1.0.zip
| Download URL | transmogrify.xmlsource-1.0.zip |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e47307ca587520e3ba2fe2fb4b8d004211d9fb0c886199730b3a8808c245a62
|
|
BLAKE2b-256 checksum How to use checksums |
f9fb9babfd16224f49594cfef280218f310378caaa9565f8fc494b792972ddb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for transmogrify.xmlsource 1.0
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.