Re: [Dhis2-devs] DHIS2 Docs

Hi Lars, Just following up on this. What would the timeline look like for the implementation of POST support for resources in api/documents? Thanks, Lorill On Thu, May 12, 2016 at 3:26 PM, Lorill Crees wrote: > Thanks Lars, that is helpful. > > We have a couple of use

Re: [Dhis2-devs] DHIS2 Docs

Thanks Lars, that is helpful. We have a couple of use cases for this functionality: 1. There is a desire to upload supporting documents around particular surveys in DHIS 2. For example, there may be a Word doc with the background information around what a particular survey is about and

Re: [Dhis2-devs] DHIS2 Docs

Hi Lorill, we are not going to deprecate/remove api/documents so it is safe to use it, however like you say we do not have POST support in the API so it is a bit useless at the moment. A short-term workaround would be to simply - implement POST support for files in DocumentController - patch? ;)

Re: [Dhis2-devs] DHIS2 Docs

Thanks Morten. That's great news about web-api versioning. In regards to the /api/documents endpoint, is it possible to create a document or is it read-only? I can't find documentation on that call. Halvdan - I look forward to your responses about the current available storage methods. On

Re: [Dhis2-devs] DHIS2 Docs

I don't think there are any plans to deprecate this endpoint right now (we are hoping to have web-api versioning in 2.24, so that at least would make it easier going forward). So you can assume that endpoint will continue to live on. For the current available storage methods, I will let Halvdan

Re: [Dhis2-devs] DHIS2 Docs

Hi Morten and Team, Following up on this again. Are there still plans to deprecate the /api/documents functionality? And what are your recommendations on how we should approach the storage of dataset & program level documents? Please see my questions below. Thanks, Lorill On Mon, May 2, 2016

Re: [Dhis2-devs] DHIS2 Docs

Hi - just following up on this. Any recommendations on how we should approach the storage of dataset & program level documents? On Tue, Apr 26, 2016 at 2:13 PM, Lorill Crees wrote: > Hi All, > > I just wanted to revive this old thread regarding the storage of documents > in

Re: [Dhis2-devs] DHIS2 Docs

Hi All, I just wanted to revive this old thread regarding the storage of documents in DHIS 2. We are wanting to programatically upload files into DHIS 2 that are related to Data Sets and Programs in general, for users to be able to view/download via the DHIS 2 UI. Using the file resource

Re: [Dhis2-devs] DHIS2 Docs

Yes, eventually we could probably do that. First order of business is really to allow (external) files to be stored in lieu of the value field of DataValue. The details of how the model will look in the end is still to be decided and is very much dependent on the requirements of the storage

Re: [Dhis2-devs] DHIS2 Docs

Hello Halvdan, *We are planning on introducing files as a type for data values, as well as data elements supporting this (document, images). You would then use the datavalue model to implement these types of requirements.* ^^This is exactly what is needed by us. I didn't know this was already in

Re: [Dhis2-devs] DHIS2 Docs

Hi Halvdan Sounds great and a good alternative! I'd like to work through an example or two: We have annual performance plans made up of multiple quarterly reports so I would expect there to be 2 data sets: - Annual Performance Plans (fYear) - Quarterly Performance Reports (fQuarter) If we

Re: [Dhis2-devs] DHIS2 Docs

Hi All These are the concepts we've been thinking about: DocumentSet, DocumentSetLevel, Document. [DocumentSet] would similar to data sets in that they are cyclical. They may have different periodTypes (e.g. yearly, fYealy, quarterly, fQuarterly, onChange) and may be compulsory. These include

Re: [Dhis2-devs] DHIS2 Docs

We are planning on introducing files as a type for data values, as well as data elements supporting this (document, images). You would then use the datavalue model to implement these types of requirements. The implementation is in the works but is a fairly complex beast as we're juggling actual

Re: [Dhis2-devs] DHIS2 Docs

I don't like that we at naming the bp document. Let's file it a file api. As much as possible I want to save the wording document until we implement a proper nosql document storage. We already have /api:documents which I want to remove (I doubt many external apps depend on it) On Tuesday, July

Re: [Dhis2-devs] DHIS2 Docs

A few quick thoughts on document storage: 1. once you have a lot of documents it becomes an interesting problem finding them/searching them. People have been doing this for a LONG time and there are a couple of well understood metadata standards for storing metadata about documents (for example

Re: [Dhis2-devs] DHIS2 Docs

Hi Related to this we also have a similar requirement where the functionality for document upload is required as part of normal data entry. Basically, a person has to visit a facility for inspection and taking photos of the facility is part of that inspection. These photos then have to be

Re: [Dhis2-devs] DHIS2 Docs

Definitely agree! The working title at the moment is 'file resource', which seems to be descriptive enough and not too generic. 'Document' as it exists right now in dhis2 is really only local storage with a relative path in the DB. 'File resources' could potentially replace that (as a more

Re: [Dhis2-devs] DHIS2 Docs

Greg, As far as I know, this is just an idea that Lars and I have been chatting about. I'll bring it up during the expert academy to get wider inputs Regards calle On 27 July 2015 at 12:33, Greg Rowles greg.row...@gmail.com wrote: Hi Devs I heard there is talk for supporting document

[Dhis2-devs] DHIS2 Docs

Hi Devs I heard there is talk for supporting document storage as part of DHIS2 but I don't find any plans on launchpad. Can anyone confirm? Kind Regards, Greg -- *Health Information Systems Program - South Africa* *- - - - - - - **- - - - - - - **- - - - - - - **- - - - - - - **- - - - - *

Re: [Dhis2-devs] DHIS2 Docs

Hi Greg, You can always simply upload the supporting document as a resource and then make it available through a dashboard. Otherwise, maybe you could write a more specific blueprint? Regards, Jason On Mon, Jul 27, 2015 at 8:59 PM, Calle Hedberg calle.hedb...@gmail.com wrote: Greg, As far