These are chat archives for frictionlessdata/chat

27th
Jun 2017
Ismael Ors
@IsmiKin
Jun 27 2017 11:16
Hi guys! I don't know if any of you are awake right now. I had been working a bit with your library and I think it's awesome. I started working with the new version (1.a) and I saw the reportoutput it's different as it's generated on the goodtables-web. I want to know which one should I continue looking at or if it is possible to generate the report in different way. I'm using the class Inspector and I'm working on goodtables==1.0.0a10. I think it's because the web it's using the Pipeline class instead of Inspector, may I right?
Ismael Ors
@IsmiKin
Jun 27 2017 14:12
I have checked the docs again and this one (latest) match with the web and the Pipeline class http://goodtables.readthedocs.io/en/latest/reports.html#standalone-processor-reports . Does exists another one for Inspector?
Ismael Ors
@IsmiKin
Jun 27 2017 14:41
I found very interesting the "meta stats" on Pipeline, what it could be very interesting for the Inspector report also :) https://github.com/frictionlessdata/goodtables-py/blob/v0.5.6/goodtables/utilities/helpers.py#L74-L108
Paul Walsh
@pwalsh
Jun 27 2017 14:47
Hi @IsmiKin
Pipeline, and in general, the pre v1 API, is deprecated. goodtables-web still uses that version of the library, but probably for no more than a week now, as we are updating it as we speak.
The new Inspector class, and the new API in general, should be able to do anything the older one did (and there are less bugs).
If there is something you cant do in v1, please let us know
otherwise, consider that the report format going forward
I think one thing that was not forward ported is the report context - the rows around the row being refered to in an error. Not sure it has much value though
Ismael Ors
@IsmiKin
Jun 27 2017 14:57
Thank you for your answer @pwalsh , I made an easy UI based on the one you made for the reports and I took as reference the Pipeline one, so when I updated goodtables I realised it's doesn't match anymore. So, reading your answer I guess I have to follow the new report structure for Inspector and I have to expect it to be extend in soon future. Do you have plan to add the "meta stats"?
Paul Walsh
@pwalsh
Jun 27 2017 15:01
We have a UI for the new reports. it is already available in goodtables.io ( http://github.com/frictionlessdata/goodtables.io ) and is being ported for generic use in https://github.com/frictionlessdata/goodtables-ui
For the meat stats, can you please open an issue at https://github.com/frictionlessdata/goodtables-py/issues and describe exactly what you are looking for
Ismael Ors
@IsmiKin
Jun 27 2017 15:03
Thank you so much, it looks I was a bit "out of date", great job guys! I will open the issue soon :)
Georges L J Labrèche
@georgeslabreche_twitter
Jun 27 2017 16:16
so guys, who do I bug to get a coveralls project repository token?
Georges L J Labrèche
@georgeslabreche_twitter
Jun 27 2017 16:22
However, I don't think I need it if we're using Travis CI.
Georges L J Labrèche
@georgeslabreche_twitter
Jun 27 2017 16:30
yeah, no need.
Paul Walsh
@pwalsh
Jun 27 2017 17:30
@rufuspollock check this out https://github.com/dataship/frame
Georges L J Labrèche
@georgeslabreche_twitter
Jun 27 2017 18:44
Any preference for full data binding (POJO) vs untyped data binding when reading datapackage jsons
?
I guess this is the conversation that @danielfireman started over here: frictionlessdata/tableschema-go#3
Georges L J Labrèche
@georgeslabreche_twitter
Jun 27 2017 19:25
I noted that the datapackage.json sample have either the license String property or licenses Array property. The differentiation doesn't seem to be mentioned in the specs. Am I missing something?
Georges L J Labrèche
@georgeslabreche_twitter
Jun 27 2017 19:48

I suspect it is simply a case of the testsuits-extended repo not being updated with latest specifications? For instance, there is a property here called "maintainer": https://github.com/frictionlessdata/testsuite-extended/blob/master/datasets/currency-codes/datapackage.json

But looking at the specs it seems that that property is deprecated considering that the "contributor" object has a "role" property that can be set to "maintainer."