Package gavo :: Package registry :: Module identifiers

Module identifiers

Parsing identifiers, getting res tuples and resobs from them.

The DC-internal identifiers are, by default, formed as ivo://<authority-from-config>/<sourceRD path>/<id within path>.

Thus, all renderers of a given service have the same ivo-id, which is to say, they are all just capabilities on the same record.

Functions

computeIdentifierFromRestup(restup)
returns an identifier from a res tuple.

source code

parseIdentifier(identifier)
returns a pair of authority, resource key for identifier.

source code

getRestupFromIdentifier(identifier)
returns the record for identifier in the services table.

source code

getResobFromRestup(restup)
returns a resob for a res tuple.

source code

getResobFromIdentifier(identifier)
returns a resob for an identifier.

source code

Variables
	__package__ = `'gavo.registry'`

Function Details

parseIdentifier(identifier)

source code

returns a pair of authority, resource key for identifier.

Identifier has to be an ivo URI.

In the context of the gavo DC, the resource key either starts with static/ or consists of an RD id and a service ID.

getResobFromRestup(restup)

source code

returns a resob for a res tuple.

restup at least has to contain the sourceRD and resId fields.

The item that is being returned is either a service or a NonServiceResource (including DeletedResource). All of these have a getMeta method and should be able to return the standard DC metadata.