Kordiam provides you with the opportunity to capture and store text and files (e.g., image files) directly in Kordiam through the Content Entry feature. This allows you to attach them directly to the relevant story.
The captured content can be transferred via FTP to your editorial system, content management system, or any other system with FTP access. This creates a continuous process chain from ordering via Kordiam through content capture to further processing in the editorial system.
Here's how:
Setting up the FTP connection
In Kordiam, you have set up one or more publication platforms (e.g., a magazine, a newspaper, etc.).
Kordiam can transfer data for each platform to a directory on an FTP server.
For each publication platform, set up the connection as follows (admin rights are required):
- Go to the "Platforms" page in the admin area
- Open the relevant publication platform for editing by clicking on "Edit"
- Go to the "Advanced Settings" tab
- On this tab, you will find the input fields for the FTP server URL as well as for the FTP server login name and password (not your Kordiam password!)
- Enter the data and save it.
Reading the data
The data is transmitted in the NewsML G2 standard.
Attached to this entry, you will find sample files for text and images.
The file names consist of the following elements:
- Publication date in the format yyyymmdd
- Publication platform name (first 8 characters)
- Category name (first 8 characters)
- Title of the Story (first 30 characters)
- Format (e.g., "text")
- A unique ID assigned by Kordiam
- A version number if a user has saved a new version of the content
The individual elements are separated by a "-" character.
Within the file, you will find the following information:
-
guid + Version - A unique ID composed of a first part that identifies the Story in Kordiam and a second part for each format (e.g., "Text", "Picture", etc.). In the attached examples (see below), these are the numbers ":28226852" and ":28226862". With this two-level ID, you can group all files belonging to a Story or further process them.
When a user uploads a new version, the version counter increases by 1. - itemClass qcode - Indicates the type of content
- service qcode:"Kordiam:group" - Indicates the group (i.e., department, section, etc.) to which the story belongs
- title - Story title. This is not a headline but a general description of the story in Kordiam
- edNote role="Kordiam:task-note" - Note for each task (i.e., a special note just for a text task)
- edNote role="Kordiam:page" - The category assigned to this story
- link href - A URL that leads the user directly to the editing mask of the story in Kordiam
- creator literal - The user's initials
- description role="drol:caption" (only for images) - The image caption; this is also included in the IPTC header of the image files
- contentSet - The actual content or links to separately provided files (e.g., images)
Special features
- If a Story is moved to a different publication date, the file is transferred again with the new publication date in the file name.
- When text and images are delivered for a story, two separate XML files are transferred (one for text, one for images). Both files have a common ID component (see above "guid"), so a link between the files can be established.
- When delivering images and other files, the central image XML file refers to the image files.
- If users enter a caption for images during upload, this will be included both in the XML file and in the IPTC header of the image file.
Comments
0 comments
Please sign in to leave a comment.