Getting resources by CTID fails for some resources

[siuc-nate]

For some resources, trying to get a record by its CTID fails. For example:

http://lr-staging.learningtapestry.com/resources/ce-fcb90ae2-fa79-48f1-addf-062bd2c98985
and
http://lr-staging.learningtapestry.com/ce-registry/ce-fcb90ae2-fa79-48f1-addf-062bd2c98985
give 404s. The structure of these 404s is also different, which may deserve its own issue (but is beside the point for now).
The record, however, does exist:
http://lr-staging.learningtapestry.com/ce-registry/envelopes/2577e5cd-c5da-49ea-a5e4-ca339ea0efd5
Note the CTID in that envelope's resource matches the CTID provided in the above links.

However, other resources can be retrieved by CTID:
http://lr-staging.learningtapestry.com/resources/ce-AB30C9E1-F9E5-4C42-A2B9-CE004DD6DA2E
works, however
http://lr-staging.learningtapestry.com/ce-registry/ce-AB30C9E1-F9E5-4C42-A2B9-CE004DD6DA2E
fails

Additionally, using the search API endpoint does find it when the get endpoint fails:
http://lr-staging.learningtapestry.com/ce-registry/search?ceterms%3Actid=ce-fcb90ae2-fa79-48f1-addf-062bd2c98985

@science @cwd-mparsons Thoughts?

[leolara]

@coffeejunk I think this might be caused by the latest changes on CTID structure and perhaps the configuration do not have the new prefix or something

[coffeejunk]

http://lr-staging.learningtapestry.com/ce-registry/ce-AB30C9E1-F9E5-4C42-A2B9-CE004DD6DA2E is not a valid URL as /resources is missing from the path. The URL would have to be http://lr-staging.learningtapestry.com/ce-registry/resources/ce-AB30C9E1-F9E5-4C42-A2B9-CE004DD6DA2E or optionally with omitted community http://lr-staging.learningtapestry.com/resources/ce-AB30C9E1-F9E5-4C42-A2B9-CE004DD6DA2E

However in addition to this, the domain in the @id of the resource in question deviates from the configuration:

"@id": "http://credentialEngineRegistry.org/resources/ce-fcb90ae2-fa79-48f1-addf-062bd2c98985"

and the configuration states

"id_prefix": "http://credentialengine.org/resources/"

As such the retrieval for this particular resource will only work via the envelope.

If the desired domain is credentialEngineRegistry.org instead of credentialengine.org we can change the configuration. Alternatively we could add the option for multiple domain names for a community.

[stuartasutton]

Mulltiple domain names for a community seems unwise.

[siuc-nate]

My understanding was that ce-registry was the actual name of the community and that resources/ was just a wrapper of sorts to facilitate our particular use case of retrieval by CTID. So I thought that using ce-registry would/should work too (since another community name could be used in its place).

What would the correct URL structure be to get back a resource with some specific community name?