CPS needs to be able to store tags for each dataseries

OCHA-DAP / DAP-System

Webapp to manage DAP (workflow, data extraction)

3 stars 3 forks source link

CPS needs to be able to store tags for each dataseries #327

Open alexandru-m-g opened 9 years ago

alexandru-m-g commented 9 years ago

A dataseries can have zero or many tags. A tag is a simple string.

This is related to #298.

seustachi commented 9 years ago

Can we add any string, or do we provide a list of possible tags ? If we deceidre for the list, we have to manage the list of available tags, then the association.

I think we should do it, avoiding chaos in the tags, duplicate, etc ...

alexandru-m-g commented 9 years ago

It probably needs to be a free text field cause even on ckan the list of tags is not restricted.

If we wanted to be smart, we could show suggestion based on the existing text fields that exist in CKAN already. There's an API to get this list. But I think we can start small and just have a free text string for the beginning. @cjhendrix ?

cjhendrix commented 9 years ago

It's a good idea, but yes, we can start small and leave that for later.

seustachi commented 9 years ago

Can tags be edited in ckan ? I believe we should manage tags in one place only (like we did for metadata) and then have a one way synchronization only.

In this case, I would suggest the following :

prepare the data model on CPS side.
Replicate the current tags from ckan to CPS (again, like we did for metadata)
Implement tag management in CPS
Write the sync

An alternative would be to keep the concept of tags in ckan only, and having CPS request them only when needed.

@alexandru-m-g @cjhendrix ?

cjhendrix commented 9 years ago

Tags can be edited in CKAN, like all of the metadata we are pushing to CKAN from CPS. I think we can make the assumption that those with access to edit the indicators on CKAN understand that the edits should be made in CPS.

We could even add something to the edit interface on ckan that warns a user that they are editing an indicator and that their edits will be overwritten by CPS.

seustachi commented 9 years ago

So unless @alexandru-m-g jumps in, I will start with 1.prepare the data model on CPS side as soon as the high priority issue #330 is closed

cjhendrix commented 9 years ago

Sounds good.

alexandru-m-g commented 9 years ago

@seustachi just to make sure I undestand:

when you're saying "Replicate the current tags from ckan to CPS", you're referring to having for each CPS dataseries the list of tags that's currently in CKAN for that specific indicator.
You're NOT referring to the entire list of existing tabs ( which could be used as selection options for the user ). We still plan, at a later point, to have an autocomplete function based on the CKAN API that allows you to search through the existing tags.

Did I get it right ?

seustachi commented 9 years ago

Yes @alexandru-m-g , you got it right.

The same way we imported the metadata from CKAN, because we didn't want to lose the work done by the data team in the ckan UI.