There are multiple ways in which other systems can interact with Desk-Net. This page provides you with an overview of all the integration possibilities with Desk-Net.
The most powerful way of interacting with Desk-Net is the Desk-Net API. Learn more about it on our dedicated Desk-Net API site. Please note that Desk-Net can also connect with other systems via their API (e.g. with the cloud-based CMS MetroPublisher).
The following entry lists all the integration possibilities (including the API) by task.
In case you have questions about how to integrate with Desk-Net please send us an email (firstname.lastname@example.org).
Stories and story lists
Reading/exporting individual stories
There are two ways for using story data from Desk-Net in other systems:
- Desk-Net API: Provides you with the most comprehensive access to almost all data points associated with a story in Desk-Net.
- Content Export Feature: Desk-Net can export story data via ftp in XML files that adhere to the News ML G2 data standard. Please note that this export focuses on actual content entered or uploaded to Desk-Net on the Content Entry tab (open a story for editing in Desk-Net and click on the Content tab). While the files do comprise meta-data related to the story this export does not allow you to export as many data points of a story as the API.
Inserting individual stories
Please use the Desk-Net API if you want other systems to create a story in Desk-Net.
Reading story lists
Please use the Desk-Net API if you want to get all stories associated with a specific platform and its categories (e.g. all Sports stories planned for publication on your website).
Desk-Net handles events and appointments such as press conferences, interview appointments, a city hall meeting or a sports match.
From a structural point-of-view they are the same type of element as a story. The differentiating factor is that an element that is treated as an event/appointment by Desk-Net contains an event date (start/end; and optionally an event start and end time).
Using the Desk-Net API is the best way to read events/appointments. You can get individual appointments by ID or lists of events (e.g. all appointments related to next week's Sports pages of your website).
Besides using the API exporting events/appointments is possible on a personal level.
Every user has the possibility to subscribe with his electronic calendar (e.g. Outlook, iPhone Calendar, etc.) to a webcal feed. All his personal assignments (e.g. if he is a reporter attending a press conference) are then exported to his calendar.
The webcal feeds can be found at the bottom of the page My Desk-Net > Settings.
Inserting individual events/appointments
The Desk-Net API provides you with a way to enter new events/appointments and to edit existing ones.
Desk-Net can import event XML files via ftp from sources such as wire agencies (e.g. dpa, STT, Zapaday) or event databases (e.g. MSU Event, LeoEvent, Tempestiva).
The XML files preferably adhere to the EventsML G2 standard. However, in cooperation with the Desk-Net developer team custom formats can be imported as well.
Inserting/importing event data via an ics file is currently not possible. Please contact us at email@example.com in case such a feature is important to you.
Often a story is based on an email that has been received by the newsroom / editorial department.
The basic process to import an email is a manual one described here.
As a developer you might be interested in the possibility to send emails to Desk-Net and have them automatically converted into calendar events.
For this check the section "Automatic Import into a Calendar" in the above-mentioned support portal entry.