Spreadsheet schema fields and titles

[caprenter]

The current site: http://www.threesixtygiving.org/standard/ only offers downloads to the titles spreadsheet, and not the fields spreadsheet.

CoVE can cope with either: http://cove.opendataservices.coop/360/ but there is no documentation on the website about the fields version.

@timgdavies not sure if this is deliberate or not.

[timgdavies]

This was an attempt to simplify things - as I wasn't sure we had a clear use case where someone would prefer the field title spreadsheet when creating data.

However, we might want to find a way in the design to provide awareness of the fields version, without it being too high profile / on a par with the preferred titles version.

[ekoner]

@caprenter I've pinged this over to you but keeping it low priority.

[morchickit]

@stevieflow - isn't this relevant to the the new standard documentation?

[stevieflow]

I think we still have the same issue if you look at https://threesixtygiving-standard.readthedocs.io/en/latest/reference/#data-formats

However, @morchickit is right to flag that this should no longer be considered as part of "the website" repo

@Bjwebb @caprenter is it going to be useful for us to have a separate repo for documentation "website" issues (navigation / content) , or should we just post in https://github.com/ThreeSixtyGiving/standard and add relevant labels?

[caprenter]

The reason the website has a repo is because there is code here that needs to be deployed and worked on to run the wordpress website, with additional code and plugins to display the 'standard' within the wordpress.

This can make it difficult for someone who spots a problem on the website to know where the right place to report it is.

We have always dealt with this by letting people report it wherever they like - we know how to deal it with it from there.

Ideally, issues with the new docs should be reported against the standard repo - that's where they are, and that's where the code to generate them sits, and that's where links to issues from the docs will point.

As Steven says, the issue presents in the same way on the new documentation, but that is because the underlying problem as outlined by Tim above still exists.

[morchickit]

Thanks @caprenter ! The problem at the moment is the https://github.com/ThreeSixtyGiving/standard is also a repo to flag issues for the standard, not only the documentation. I have a feeling that is that repo will be used for both the documentation and as a place to flag changes in the schema it will be too confusing for the users.

As much as I appreciate the approach of reporting whenever people like, I do prefer clear reporting guidelines, specifically when our users are new and need more guidance. Moreover, it would be useful for other who would like to tap in and contribute to understand the flow and not to be dependent on the Open Data Services team to guide the through. @stevieflow - maybe something to speak about on the Monday call?