Difference: Minutes20thMarch2017 (1 vs. 3)

Revision 32017-03-24 - KarlVyhmeister

Line: 1 to 1
 
META TOPICPARENT name="SedmTeamMeetings"

SEDM web site meeting

Line: 10 to 10
 During this meeting (and the one taken on 10th March), several new functionalities are requested.

  • When an object is searched, a hyperlink is displayed with the information of object. This will be a summary page of the object with all exposures taken within that project ID. Then it can contain a note on the status of the observation (weather conditions, etc.). How many exposures has been taken, with which FWHM, who was the requester, and the link to the data. From there you can place a new request.
Changed:
<
<
  • Put a link to SEDM in the header.
>
>
  • Put a link to SEDM in the header. (done)
 
  • Place the flask web site code in a different directory from SEDMdb. The DB code shall be importable from the web site. (update: code is now in kpy/flask)
  • Create a form to introduce a new object. This is a different form for different classes of epochs: extragalactic, variable or SSO.
  • Summary page with the past, current and scheduled exposures for the SEDM.

Revision 22017-03-24 - KarlVyhmeister

Line: 1 to 1
 
META TOPICPARENT name="SedmTeamMeetings"

SEDM web site meeting

Line: 11 to 11
 
  • When an object is searched, a hyperlink is displayed with the information of object. This will be a summary page of the object with all exposures taken within that project ID. Then it can contain a note on the status of the observation (weather conditions, etc.). How many exposures has been taken, with which FWHM, who was the requester, and the link to the data. From there you can place a new request.
  • Put a link to SEDM in the header.
Changed:
<
<
  • Place the flask web site code in a different directory from SEDMdb. The DB code shall be importable from the web site.
>
>
  • Place the flask web site code in a different directory from SEDMdb. The DB code shall be importable from the web site. (update: code is now in kpy/flask)
 
  • Create a form to introduce a new object. This is a different form for different classes of epochs: extragalactic, variable or SSO.
  • Summary page with the past, current and scheduled exposures for the SEDM.
  • Home page with statistics oh how many hours has been spent for each project. This will be different for Admin, who can see all the information on all the projects, and users, who can see how much time they have spent from their project time. Also, what objects has been requested by the group and how much time they have spent on each object already.

Revision 12017-03-20 - NadiaBlagorodnova

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="SedmTeamMeetings"

SEDM web site meeting

Attendees: Richard, Karl, Nadia

Update on SEDM web site

  • Karl has created the basic SEDM web interface that allows to search for objects in the DB.

During this meeting (and the one taken on 10th March), several new functionalities are requested.

  • When an object is searched, a hyperlink is displayed with the information of object. This will be a summary page of the object with all exposures taken within that project ID. Then it can contain a note on the status of the observation (weather conditions, etc.). How many exposures has been taken, with which FWHM, who was the requester, and the link to the data. From there you can place a new request.
  • Put a link to SEDM in the header.
  • Place the flask web site code in a different directory from SEDMdb. The DB code shall be importable from the web site.
  • Create a form to introduce a new object. This is a different form for different classes of epochs: extragalactic, variable or SSO.
  • Summary page with the past, current and scheduled exposures for the SEDM.
  • Home page with statistics oh how many hours has been spent for each project. This will be different for Admin, who can see all the information on all the projects, and users, who can see how much time they have spent from their project time. Also, what objects has been requested by the group and how much time they have spent on each object already.
  • The page with the request shall show that the request has expired if that is the case.
  • The end-of-night report shall be an HTML page showing all the data taken so far. And sending the email to the users who requested the reports. Also, an automatic page being generated for admin level only to show what was observed during that night.

-- NadiaBlagorodnova - 20 Mar 2017

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback