recast-hep / recast-frontend Goto Github PK

The code for the RECAST website (also providing RESTful API).

License: Other

JavaScript 1.26% PHP 75.76% CSS 22.98%

recast-frontend's Introduction

The RECAST front-end

This is the Drupal code for the RECAST front-end and RESTful API currently hosted at http://recast.perimeterinstitute.ca

As RECAST is a community project, we are moving to GitHub for collaborative development. RECAST packages (eg. API wrappers, back-end implementations etc.) should be in repositories named recast-<package>

recast-frontend's People

Contributors

Stargazers

Watchers

Forkers

dwindibank

recast-frontend's Issues

API not following audience parameter

I discovered another issue with the API. I'm trying to create a request using a selective audience. Take this example:
curl --data "username=lheinric&reason-for-request=bla reas&model-type=bla model&analysis-uuid=1f3dbc55-5100-9284-4519-aac16f60988d&activate=1&subscribers=backend-rivet&title=z3&predefined-model=bla pre&audience=selectivexxx" http://recast.perimeterinstitute.ca/dev/api/recast-request.json

as you can see the audience is set to 'selective' but unfortunately it always ends up as 'all' on the PI side. Editing on the web interface works though.

the corresponding line in PHP seems to do the correct thing, so I'm not sure what is going on

recast-frontend/modules/recast_api/recast_request_api.inc

Line 63 in fd49d6f

$node->field_recast_audience[$node->language][0]['value'] = $data['audience'];

Results upload should be tied to point request

Currently there is one response per request, but one request might have several parameter points.

api/recast-request/%uuid% not returning Audience or Subscribers

The api is not returning audience or subscribers for a get call for a particular uuid (i.e. api/recast-request/%uuid%).

API not following audience parameter

associate reference metadata to request

Hello,

it would be great if we could add references (doi,eprint, journal, inspire) to requests the same way we do that for analyses. The reason is that semantically, the request is associated to a theorist's work (maybe a paper) while the analysis is associated to an experimental result/paper. Adding this functionality will help correctly attibuting the RECAST request to the underlying papers.

Cheers,
Lukas

Analysis API (api/recast-analysis) not returning ownership and owner correctly

'ownership' => ($n->field_analysis_ownership[$lang][0]['value'] == 0) ? t('Unowned') : t('Owned'),
'owner' => $n->field_analysis_owner[$lang][0]['value'],

eprint field not filled correctly in API vs Website

Hi,

there seems to be a mismatch between the information available on the website vs the one I get via the API. For example:

http://recast.perimeterinstitute.ca/dev/api/recast-analysis/1f3dbc55-5100-9284-4519-aac16f60988d

shows only a journal reference, while the corresponding node on the website

http://recast.perimeterinstitute.ca/dev/?q=node/794

also has an eprint, and inspire field filled.

Cheers,
Lukas

API should provide URL to analysis, request, result

With info from API, we can't make a link to the corresponding request, analysis, etc. on the webpage

Set up Semantic Urls

Need to enable Pathauto module, and setup patterns for each type.

(UI) Request: Analysis field should be a link

Change API code to Entity API

The API code uses Drupal Arrays, this should be switched to using the Entity API (PHP objects).

Add mathjax support

   <script type="text/x-mathjax-config">
      MathJax.Hub.Config({tex2jax: {inlineMath: [['$','$'], ['\\(','\\)']]}});
    </script>
    <script type="text/javascript"
      src="//cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML">
    </script>

    <script type="text/javascript">
        MathJax.Hub.Config({
          TeX: {
            Macros: {
              TeV: "\\mathrm{TeV}",
              pT: "p_\\mathrm{T}",
            }
          }
        });
    </script>

(UI) Recast Request-Selected Subscribers not showing consistently

Recast Request-Selected Subscribers not showing consistently: when audience is "selective" not all values seem to be shown.

Remove restrictions related to file types

File Types

There are some restrictions on the files. Still need to know what can be uploaded. Just need a comma separated list of file extensions.

recast-response->result-file (ROOT file with TH1) is currently: lhe, zip
recast-response->result-text-file (Multiple Parameter Response) is currently: txt

Also for the LHE point files:
request->parameter-points->run-condition->lhe-file is currently: lhe, zip, txt, jpg

File Size

Currently files are restricted to 512 MB ... seems small.

File Location

recast-response->result-text-file (i.e. field_result_text_file) needs to have it's directory set. Could just be the same directory (recast_results) as the other field

Turn on revisions by default for recast content types

API should provide analysis->request and request->analysis mapping

Add API for users

Analysis > List request should be sorted chronologically

for example:
http://recast.perimeterinstitute.ca/dev/?q=node/453/listrequests

Add associated DOIs to response

Hi,

more ideas :)

We are in the process of integrating with services that will associated DOIs. We would like to be able to associate a DOI at two places:

at request creation/update:
a DOI will be minted for the request made by the "theorist" and will be associated to the original paper that motivated the request. probably the right place to add this is in the "Update a Request/Create a Request" API endpoints. In the end a request should have a new property, perhaps called 'recast-request-doi' (to differentiate it with a possible doi for its reference
when uploading a response

a response should likewise have a 'recast-response-doi' which will be minted as a supplement to the underlying analysis

Thanks,
Lukas