Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Custom resource for Akvo web project updates #463

Closed
zzgvh opened this issue Mar 14, 2014 · 9 comments
Closed

Custom resource for Akvo web project updates #463

zzgvh opened this issue Mar 14, 2014 · 9 comments
Assignees
@zzgvh
Milestone
2.3.5 Uglyfruit

Comments

@zzgvh
Copy link
Contributor

zzgvh commented Mar 14, 2014

See akvo/akvo-web#167
zzgvh added a commit that referenced this issue Mar 14, 2014
@zzgvh
[#463] Add project_update_extra API resource
294dc61 
The project_update_extra resource adds some data from User and
Organisation to the normal project_update resource. This is needed for
the JSON-fetching plugin on akvo.org since it needs all data in one go
(or at least that makes things very much simpler).
@zzgvh zzgvh mentioned this issue Mar 19, 2014
Closed
zzgvh added a commit that referenced this issue Mar 19, 2014
@zzgvh
[#463] Extend schema description of project_update_extra
8fc554f 
Extend the schema with a description of the User and Organisation data inlined in the "user" field.
@adriancollier adriancollier added this to the 2.3.5 Uglyfruit milestone Mar 24, 2014
@adriancollier
Copy link
Contributor

Something that is worth considering, is the ability for us to post Test or Demo updates.

These could then be excluded from certain stats and/or activities such as the API.

However we need to be careful that this is not used as a validation tool for organisations to filter the updates being sent in by partners before they are fully published. If we were to decide that this functionality is required and needs to be built then we should build something for that and not allow for this to be created or managed in an indirect manner.

@adriancollier
Copy link
Contributor

@zzgvh is this the same or different from #463

@zzgvh
Copy link
Contributor Author

zzgvh commented Apr 4, 2014

I think your reference is wrong Adrian, this is #463...

@zzgvh
Copy link
Contributor Author

zzgvh commented Apr 4, 2014

Seems to me the easiest way to filter out test updates is to have a setting with a list of projects that we consider test projects, meaning updates to those are test updates. Much trickier to filter out individual updates. What criteria would we use?

@adriancollier
Copy link
Contributor

Sorry I meant #306

@adriancollier
Copy link
Contributor

In relation to test updates, I think updates on http://rsr.akvo.org/project/2/ should be seen as test updates, and all other projects should only contain real updates.

@adriancollier
Copy link
Contributor

@zzgvh is this in #306?

@adriancollier
Copy link
Contributor

Code is now merged into develop - closing this issue, but still need to confirm if this also covered #306

@zzgvh
Copy link
Contributor Author

zzgvh commented Apr 7, 2014

Ya, and the final resource for akvo.org might need tweaking too. But this is a step on the way.

@KasperBrandt KasperBrandt mentioned this issue May 12, 2014
Closed
@stellanl stellanl mentioned this issue May 14, 2014
Closed
@MichaelAkvo MichaelAkvo moved this to Done in RSR Dec 8, 2022
@MichaelAkvo MichaelAkvo added this to RSR Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zzgvh zzgvh

Labels
None yet
Projects
RSR
Archived in project
Milestone
2.3.5 Uglyfruit
Development

No branches or pull requests
2 participants
@zzgvh @adriancollier