Adrià Mercader

This sounds indeed like a bug on the URI parsing on the processors or the functions that guesses the URIs when serializing, I'll have a look when I have a...

hi @VladimirAlexiev thanks for the feedback! You are correct regarding literals vs resources. We fix this in the code (#66) but not on the examples. Would you mind submitting a...

@maxclac Looks like the SchemaOrg profile used to generate the JSON-LD snippet that Google Dataset Search will parse expects [`temporal_start` and `temporal_end`](https://github.com/ckan/ckanext-dcat/blob/6b7ec505f303fb18e0eebcebf67130d36b3dca82/ckanext/dcat/profiles.py#L1519) to be the field names. Can you try...

Summary of changes: **dcat:Dataset** - [x] Add dct:accessRights - [x] Add foaf:page (documentation) - [x] Add dct:provenance - [x] Add dct:type - [x] Add dct:relation - [x] Add dct:hasVersion (dataset)†...

The issues you mention are known: > - literals instead of RDF resources See #50 (This should be easy to fix if you are up for a PR) > -...

Thanks @akuckartz

On CKAN>=2.9 you need to use the `ckan` command instead of the `paster` one: ``` ckan -c ../ckan/ckan.ini generate-static json out.json ``` The command runs but I see that it...

@memaldi I'm not sure what you are trying to fix is a bug. The original behaviour was to look for the user name is a global CKAN configuration setting (`config['ckanext.harvest.user_name']`),...

You are absolutely correct @memaldi, sorry, I hadn't looked at the source config options in a while. Your patch makes sense now, but there's no need to remove the `config['ckanext.harvest.user_name']`...

@mattfullerton is this still an issue?