[Fiware-tools] Publishing the Tools on the Catalogue

[Yosu Gorroñogoitia]

Hi All,
If I understand well, it is still not possible to include new tools to
the production catalogue. Let us now when it is possible to proceed.
Regards
Yosu

On Mon, 2013-11-04 at 16:33 +0100, Davide Dalle Carbonare wrote:
> Dear Pedro,
>     I guess we already talked about this during one of the last conf
> calls ...
> If I remember right we decided to keep the same structure as for the
> GEis
> and report an appropriate text where the tab information do not apply
> for
> for the tool.
> I suggest to proceed along this line.
> 
> I remind to all the partners that the entries in the Catalogue will
> follow the
> same validation process adopted for the GEis.
> You, as tool owner, can insert the information and once done, you have
> to
> change the state to "review needed" in order to ask for validation and
> publishing. (Pedro, correct me if I reported something wrong)
> 
> BR
> Davide
> 
> On 31/10/2013 11:21, Pedro Rodriguez wrote:
> 
> > Dear all,
> > 
> > 
> > In the last conference, we discussed publishing the new Tools
> > section of the Catalogue in the production environment.
> > Before doing that we have to agree on the final configuration we
> > want.
> > I’ll summarise what there is in the development Catalogue right now:
> > 
> > 
> > Tools are created using the same procedure as a Generic Enabler but
> > selecting the “Tools” Chapter, an empty tool has the following tabs:
> > (Format Tab name - default text)
> > 
> > 
> > - Overview - mandatory
> > 
> > 
> > - Documentation: 
> > No documentation is available for this enabler 
> > If you are the administrator of this enabler, please edit this page
> > to add documentation.
> > 
> > 
> > - Downloads: There are no downloads available for this enabler.
> > 
> > 
> > - Instances: There are no instances of this Generic Enabler yet.
> > 
> > 
> > - Terms and Conditions: 
> > No terms and conditions are available for this content.
> > If you are the administrator of this content, please edit this page
> > to add the terms.
> > 
> > 
> > NOTE: There is a base text for the terms and conditions provided by
> > TID that was distributed to GE Owners via email
> > 
> > 
> > ——————————————————————
> > So, in the development instance, the only difference is the Creating
> > Instances tab that I was asked to remove.
> > 
> > 
> > In my opinion, the parts that make less sense for the Tools are the
> > ones about instances. Furthermore, the Tools already in the
> > Development Catalogue don’t use the Instances tab. 
> > 
> > 
> > My recommendation at this point is to port this to the new Catalogue
> > without the “Creating Instances” or the “Instances” tab. 
> > No additional “default” text is needed, only changing “enabler” for
> > “enabler/tool” in some cases.
> > The only minor issue to discuss is how to provide the Terms and
> > Conditions compared to the GEs (Do we use the text provided by TID?)
> > 
> > 
> > This would be quite fast to implement in the Production Catalogue.
> > 
> > 
> > 
> > 
> > Please tell me what you think or if you prefer to discuss this in
> > the next conference call.
> > 
> > 
> > Best Regards
> > -- 
> > Pedro Rodríguez
> > 
> > 
> > _______________________________________________
> > Fiware-tools mailing list
> > Fiware-tools at lists.fi-ware.eu
> > https://lists.fi-ware.eu/listinfo/fiware-tools
> 
> _______________________________________________
> Fiware-tools mailing list
> Fiware-tools at lists.fi-ware.eu
> https://lists.fi-ware.eu/listinfo/fiware-tools

-- 
Jesús Gorroñogoitia
Software Architect
Service Engineering & IT Platforms Lab
ATOS Research & Innovation

Albarracin 25
28037 MADRID
T +34 91 214 8175
F +34 91 754 3252
www.atosresearch.eu


------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended 
solely for the addressee; it may also be privileged. If you receive 
this e-mail in error, please notify the sender immediately and destroy it. 
As its integrity cannot be secured on the Internet, the Atos 
group liability cannot be triggered for the message content. Although 
the sender endeavours to maintain a computer virus-free network, 
the sender does not warrant that this transmission is virus-free and 
will not be liable for any damages resulting from any virus transmitted. 

Este mensaje y los ficheros adjuntos pueden contener informacion confidencial 
destinada solamente a la(s) persona(s) mencionadas anteriormente 
pueden estar protegidos por secreto profesional. 
Si usted recibe este correo electronico por error, gracias por informar 
inmediatamente al remitente y destruir el mensaje. 
Al no estar asegurada la integridad de este mensaje sobre la red, Atos 
no se hace responsable por su contenido. Su contenido no constituye ningun 
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. 
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor 
no puede garantizar nada al respecto y no sera responsable de cualesquiera 
danos que puedan resultar de una transmision de virus. 
------------------------------------------------------------------