Publishing separate humanitarian files


(Melinda Cuzner) #1

To be able to publish humanitarian data on a daily or weekly basis Sweden will need to publish their humanitarian data separate from the ordinary publication. We are wondering what will be the best publishing routine?

Until we are ready to merge our ordinary publication with the humanitarian data, there will be some double-counting as the new humanitarian activities are also presented in the ordinary file.

Unless we can find another way around it, removing the humanitarian activities completely from the ordinary publication would make too much of a dent in the other publications that use our data.


(Pelle Aardema) #2

Hi Melinda,

I think this approach will cause problems for users of the data. How will they know which of the published activities is the “valid” version: the one in the humanitarian dataset or the one in your regular publication?

Therefore IATI requires the iati-identifier to be globally unique, meaning

The iati-identifier must be unique for every iati-activity within the complete dataset published.


(Melinda Cuzner) #3

Thank you for replying so quickly. Since we publish one part of the data on a monthly basis and we wish to publish the humanitarian on a daily basis, we need to find a way to get around that.


(Wendy Rogers) #4

Thanks for raising @Melinda and I can see that there could be some benefit from humanitarian activities being published in their own set of IATI XML files as it would mean that data users who are only interested in humanitarian data would not need to process all of an organisation’s published XML datafiles in order to find the data that they want to use. However, I can anticipate that it may also be necessary to establish a Registry or other mechanism that would enable data users to programmatically identify which files only contain humanitarian data (rather than relying on manual selection)?

Also, as you and @pelleaardema point out the relevant activities should not be published twice so good to know that you are already working on this issue.

It would also be really interesting to hear from other publishers about any plans to segment (or not?) their data or if there are any issues that such an approach might cause?


(Melinda Cuzner) #5

Okey, I’m a bit worried of changing too much to our ordinary publication-routine. the humanitarian activities must have different identifiers from our ordinary files because they are a more detailed view of the acitivities.

I guess we could have semi-static “ordinary” acitivity data that is only updated together with the humanitarian data that is updated daily. I will have to check with our developers. And I realize I haven’t done my home work, but that would require that we can destinguish between the humanitarian activity description from the ordinary description whereas the first is the same for all activities under the same agreement and the latter is unique for that humanitarian activity. The same will be for titles and activity dates.

I will have to look into the details but I’m thinking maybe this is where we could use the hierarchylevels? Just brainstorming…