Opened 5 years ago

Closed 4 years ago

Last modified 3 years ago

#307 closed enhancement (fixed)

external names should use rasdaman, not petascope

Reported by: pbaumann Owned by: uagha
Priority: major Milestone: 9.0
Component: petascope Version: 8.3
Keywords: Cc: pcampalani, pbaumann, dmisev, abeccati
Complexity: Easy

Description (last modified by dmisev)

In many places "petascope" is used, eg, war files, in WPS ("petascope.wps.n52.ProcessCoverages?"). This is confusing for the users of rasdaman, branding should be uniform - in the end, petascope is just one out of many rasdaman components. Hence, in all code the naming should be replaced accordingly.

Endpoints are to be renamed as follows:
/rasdaman (landing page with desctiption of server and pointers to available endpoints)
/rasdaman/ows (landing page for OGC Web Services, with pointers to second level ones)
/rasdaman/ows/wps
/rasdaman/ows/wms
/rasdaman/ows/wcs : including extensions such as WCS-T
/rasdaman/ows/wcps
/rasdaman/rasql : endpoint for the upcoming web interface to rasql

The sources for the landing pages are in source:applications/petascope/templates

Documentation for upcoming 9.0 to be updated accordingly

Attachments (1)

t307-renamed-war-and-endpoints-to-rasdaman.patch (3.8 KB) - added by abeccati 4 years ago.
interim work

Download all attachments as: .zip

Change History (22)

comment:1 Changed 5 years ago by dmisev

Maybe we should also change the package structure in petascope from petascope.* org.rasdaman.*

comment:2 Changed 5 years ago by pbaumann

...and rephrase the petascope default HTML page.

comment:3 Changed 5 years ago by abeccati

Looks related to #270

There we had different endpoints but we can resume to have a single "rasdaman" root

/rasdaman (landing page with desctiption of server and pointers to available endpoints)
/rasdaman/ows : single endpoint for all OGC web services interfaces (WCS, WMS, WCPS, etc)
/rasdaman/rasql : endpoint for the upcoming web interface to rasql

comment:4 Changed 4 years ago by abeccati

  • Cc cmppri pbaumann dmisev added
  • Complexity set to Easy
  • Description modified (diff)
  • Status changed from new to assigned

As the codebase stands now, we'd like to avoid checking which service request is for which service type but want to keep them grouped so we can change our mind in future without having a new (common endpoint to define = ows).

Updating accordingly, that will be the 9.0 endpoint definition.

comment:5 Changed 4 years ago by abeccati

  • Description modified (diff)
  • Priority changed from minor to critical

Adding detail for wcst interface (supported by WCS). Linkning and superseding (opted for separate endpoints for now) ticket #270 (Raising priority to that of superseded one).

comment:6 Changed 4 years ago by abeccati

  • Cc pcampalani added; cmppri removed

comment:7 Changed 4 years ago by pbaumann

shold we use lowercase wcs etc. for homogeneity?

comment:8 Changed 4 years ago by dmisev

I vote for lowercase.

I'll still say that the /ows doesn't bring anything essential but 4 redundant bytes.

comment:9 Changed 4 years ago by abeccati

  • Description modified (diff)

Indeed all lowercase sounds good, updated

comment:10 Changed 4 years ago by abeccati

  • Status changed from assigned to accepted

Changed 4 years ago by abeccati

interim work

comment:11 Changed 4 years ago by abeccati

  • Status changed from accepted to assigned

Attached patch changes external names (and war archive also) to rasdaman

I cannot test it due to:
https://groups.google.com/forum/#!topic/rasdaman-dev/HakA4S47UUs

There are still few things to be addressed:
/rasdaman (landing page with desctiption of server and pointers to available endpoints)
/rasdaman/ows (landing page for OGC Web Services, with pointers to second level ones)
/rasdaman/ows/wcs : including extensions such as WCS-T (done but requires dedicated class to handle versions and extensions such as wcs-t, relies on petascope interface for now)

Futhermore, sending a WCS request gives a null pointer exception while sending it to the "nonexistant" ows/wcs2 endpoint gets a complaint about version

Feel free to pick it up and build on it for testing

comment:12 follow-up: Changed 4 years ago by pcampalani

Patch submitted, but keep the ticket open until we solve the issues listed by Alan in comment:11, that is:

  • missing landing pages;
  • WCS servlet to be unique for different versions and extensions.

This means, if I'm not wrong, that PetascopeInterface will probably be dropped or strongly revised.

comment:13 in reply to: ↑ 12 Changed 4 years ago by pcampalani

See changeset:40a95ec.

Replying to pcampalani:

Patch submitted, [...]

comment:14 Changed 4 years ago by abeccati

I think /rasdaman/ows can be covered by the current petascope landing page (or a revision of it I guess) while the server level one should hold overall server/endpoints info

comment:15 Changed 4 years ago by dmisev

  • Description modified (diff)

comment:16 Changed 4 years ago by dmisev

  • Owner changed from abeccati to uagha
  • Priority changed from critical to major

Assigning to Uneeb for the landing page beautification and fixing.

comment:17 Changed 4 years ago by pcampalani

RPM generation fixed in changeset:087be0b (.war filename from petascope to rasdaman).

comment:18 Changed 4 years ago by abeccati

Looks like the new interfaces are in place now, we should close this ticket on 9.0 milestone and file a new one for the remaining beautification so that the change in interface endpoint is clearly belonging to 9.0.

comment:19 Changed 4 years ago by pbaumann

  • Resolution set to fixed
  • Status changed from assigned to closed

make sense, so doing that.

comment:20 Changed 3 years ago by pcampalani

Has a ticket been spawned for remaining unresolved issues on this?

comment:21 Changed 3 years ago by pcampalani

  • Cc abeccati added
Note: See TracTickets for help on using tickets.