{22} Trac tickets (2647 matches)

Discussion between John and Peter:

Given we can identify a document, does the disappearance of a document from a registered source imply the disappearance of the metadata (such that we delete packages once the documents disappear from the registered source)?

I would expect a more explicit 'delete'. The UKLP Use Case Library describes this as "withdraw a dataset or service from publication" (part of UCD03 Maintain resources).

Wish to fold service records into package resources. Trouble is that service records don't necessarily refer to a data record, so should this be a new package?

To do this for the UKLP, the Ordnance Survey would need to add to their map service an operation to return image for a given bounding box, and COI would need to present the image on the search result page.

Otherwise, it would be possible to use Google.

This seems to require doing something else with such a group's 'delete' button, such as showing it greyed, or perhaps not showing it at all.

Where said "v0.4" would be the result of converging four lists mentioned in requirement #711.

So that Drupal doesn't need to make any adjustments to the form, and risk data being lost on submission.

Hi Will, this is important again because some CSW servers we use have over 300 documents in. Could you take a look at modifying the filter please?

This has once again been ruled out for UKLP for the timebeing.

Should return something sensible (currently reports an error).

We need a condition for 'disappears'. Asked AW about this (prob. in July) but should chase for an answer.

Scope of CSW guidance document has been broadened to include WAF.

Needs to delete all harving jobs and harvested documents, and probably to purge all packages (perhaps just delete?).

This needs more analysis, but the GEMINI2 attribute "metadata point of contact" must be reconciled with the registered publisher (or agent).

This might also be used to filter records harvested from a CSW source, but filtering also needs more analysis, as does distinction between agent and provider.

Implies that last harvested time must be stored on source by harvesting job (see #802).

As a system developer, I want to run 'create next migration version' script, so that I don't have to create migration version tests and files manually.

"when logging into ​http://register.data.overheid.nl/ with OpenID, the /user/me page gives a 404. CKAN version 1.3.4."

n the manual it says an API key kan be created via ​http://test.ckan.net/user/me /. However, when I try the corresponding ​http://register.data.overheid.nl/user/me, I get a 404 error (not found).

Summarise final set of requirements for this and finish development and test. Estimated 10 working days.

Estimate 2 days to finish dev and test.

David can you add any info needed here?

Estimated 4 weeks of Adria's time. I guess this will need to be broken down into more tickets. This feature is being requested by a number of potential customers and we have some ideas of requirements between Rufus and Jilly for this. This is the most popular new feature we talk about to new clients.

Basic websotre exists but this may be not what is described yet.

CKAN provides a rich API for the data itself, allowing users to query retrieve and use data instantly from datasets in CKAN without needing to download or process it first.