Difference between revisions of "EGI-InSPIRE:Amb 2013-11-19"

From EGIWiki
Jump to: navigation, search
Line 1: Line 1:
{{TOC_right}}
+
{{TOC_right}}[[Activity Management Board#From_October_2013|Back]] to the AMB wiki home page
[[Category:EGI-InSPIRE]]
+
 
 +
= Activity Reports  =
 +
 
 +
== NA1 == <!-- Catherine -->
 +
 
 +
== NA2 == <!-- Sergio -->
 +
 
 +
=== AppDB (19/11/2013) ===
 +
 
 +
*Outdated sw items has been enabled into production
 +
::*A monthly email is sent to sw entry owners after 3 years of inactivity.
 +
::*'Freshness' option has been added to the faceted search mechanism.
 +
*First steps for personalize the home page of the logged in users, have been made [1].
 +
*A structure for the Scientific classification API has been proposed to EGI [2]. Waiting for feedback in order to start the implementation.
 +
 
 +
<o:p>&nbsp;</o:p>
 +
 
 +
'''Ongoing tasks:'''
 +
 
 +
*Integration with the Operation portal secured API, in order to get each user roles (this info will be needed for the VO image lists management)
 +
*Investigating alternative Authentication mechanisms to cover the login process into our service (Portal + API). The selected approach should offer the ability for the user to login either using his egi sso username/password or his personal certificate. The aim is the final solution to be expandable to third-party authentication sources as well (i.e. facebook etc.)
 +
 
 +
<o:p>&nbsp;</o:p>
 +
 
 +
'''Next tasks:'''
 +
 
 +
*Fetching user details from VOMS servers about their VO membership.
 +
*Change the authentication mechanism based on the outcome of the investigation that we are currently performing.
 +
*Extend the authorization module in our system in order to map VO related permissions to the existed of future user profiles.
 +
*Implement a separate permissions tab for every registered sw/va item, from where the owner could set/unset by whom the given item will be accessible and/or managed.
 +
*Extend the software (not the VAs) items metadata in order the user to be able to set the license under which an item is available.
 +
 
 +
'''&nbsp;'''
 +
 
 +
'''&nbsp;'''
 +
 
 +
[1]. https://appdb-dev.marie.hellasgrid.gr/ (... and login)
 +
 
 +
 
  
[[Activity_Management_Board#From_October_2013| Back]] to the AMB wiki home page
 
  
= Activity Reports =
 
  
== NA1 ==
+
== SA1 == <!-- Malgorzata -->  
<!-- Catherine -->
 
  
== NA2 ==  
+
== SA2 == <!-- Peter -->  
<!-- Sergio -->
 
  
== SA1 ==  
+
== SA4 == <!-- Michel -->  
<!-- Malgorzata -->
 
  
== SA2 ==  
+
== JRA1 == <!-- Diego -->  
<!-- Peter -->
 
  
== SA4 ==
+
= Participants  =
<!-- Michel -->
 
  
== JRA1 ==
+
= Discussion  =
<!-- Diego -->
 
  
= Participants =
+
[[Category:EGI-InSPIRE]]
= Discussion =
 

Revision as of 12:19, 19 November 2013

Back to the AMB wiki home page

Activity Reports

NA1

NA2

AppDB (19/11/2013)

  • Outdated sw items has been enabled into production
  • A monthly email is sent to sw entry owners after 3 years of inactivity.
  • 'Freshness' option has been added to the faceted search mechanism.
  • First steps for personalize the home page of the logged in users, have been made [1].
  • A structure for the Scientific classification API has been proposed to EGI [2]. Waiting for feedback in order to start the implementation.

<o:p> </o:p>

Ongoing tasks:

  • Integration with the Operation portal secured API, in order to get each user roles (this info will be needed for the VO image lists management)
  • Investigating alternative Authentication mechanisms to cover the login process into our service (Portal + API). The selected approach should offer the ability for the user to login either using his egi sso username/password or his personal certificate. The aim is the final solution to be expandable to third-party authentication sources as well (i.e. facebook etc.)

<o:p> </o:p>

Next tasks:

  • Fetching user details from VOMS servers about their VO membership.
  • Change the authentication mechanism based on the outcome of the investigation that we are currently performing.
  • Extend the authorization module in our system in order to map VO related permissions to the existed of future user profiles.
  • Implement a separate permissions tab for every registered sw/va item, from where the owner could set/unset by whom the given item will be accessible and/or managed.
  • Extend the software (not the VAs) items metadata in order the user to be able to set the license under which an item is available.

 

 

[1]. https://appdb-dev.marie.hellasgrid.gr/ (... and login)



SA1

SA2

SA4

JRA1

Participants

Discussion