The Content Entry feature in Desk-Net allows you to have users enter text and upload files (e.g. pictures from a freelance photographer).
This content can then be exported via ftp connection to your editorial system, content management system or any other ftp server. Using this feature you are creating a seamless flow of information and data from planning and scheduling a story, assigning it to a user, receiving the content and handing it over to your editorial system for further processing.
This is how you set up Desk-Net to export the data:
Setup of the ftp connection
You have one or more publication channels such as a magazine, newspaper, etc. set up in Desk-Net.
Desk-Net can export content into one folder on an ftp-server per publication channel. This is how you set up the connection from Desk-Net to your ftp server (you need admin rights for this):
- Go to the page "Publication Platforms" in the admin area of Desk-Net
- Open the appropriate channel by clicking on "Edit"
- Select the tab "Advanced settings"
- Enter the ftp server details (URL, login name, password) and save your entries.
The link "Test your ftp connection" allows you to test the connection.
Should Desk-Net later on lose the connection to the ftp server it will automatically send out emails notifying all of your company's Desk-Net administrators.
XML data content
Desk-Net is exporting the data in the NewsML G2 standard.
You can find some sample files at the end of this support portal entry.
The file names are composed of the following data:
- Publication date in format yyyymmdd
- Name of publication channel (first 8 characters)
- Name of section/page (first 8 characters)
- Story title (first 30 characters)
- Format (e.g. "text" or "pict"; 4 characters)
- A unique task ID (e.g. "000001210857" for that text task, picture task, etc.). Not the Story ID.
- A version number in case a user uploads a new version of the content
Inside the files you can find this information (and more):
- guid + version - a unique ID that is comprised of two parts. The first part denotes the entire story that can contain a text task, picture task etc. The second part of the ID is unique per transferred XML file and therefore unique for each text file, picture file etc. In the sample files attached below they are the ":28226852" and ":28226862". The first part unique to a story allows you to group all files sent out per story whereas the second part makes sure every piece of content has its own unique identifier.
- itemClass qcode - Type of data such as "text"
- service qcode:"Desk_Net:group" - the group (e.g. department, desk, team) the story belongs to; "Sports desk" for instance)
- title - the story's description in Desk-Net. This is not the title as in a headline or so.
- edNote role="Desk-Net:task-note" - the text of a potential note related to the content ("task note" in Desk-Net)
- edNote role="Desk-Net:page" - The category (e.g. page) to which the content has been assigned to
- link href - a URL that takes the user straight to the editing mask of the story in Desk-Net
- creator literal - the screen name of the user who has entered the content
- headline (for text only) - the headline
- description role = "drol:teaser" (for text only) - the lead
- description role="drol:caption" (for pictures only) - the caption, though the caption can also be found in the IPTC header of the picture files
- contentSet - the actual content (for text formats) or the links to the files (e.g. picture files) that had been sent separately
Good to know
- In case the publication date is changed in Desk-Net a new file with a new file name will be exported.
- If a story contains both text and pictures two separate XML files will be exported (they contain an ID that allows you to group them - see above)
- An XML picture file will be accompanied by the actual picture files.
- If a user uploads a jpg file and enters a caption this caption will be available both in the IPTC header of the file as well as in the XML picture file.