Fileexchange & Atoms resources hidden to Open Search engines

classic Classic list List threaded Threaded
5 messages Options
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Fileexchange & Atoms resources hidden to Open Search engines

Hello,

Beeing a sharer on Scilab Filexchange, i was wondering
about why resources uploaded there are not referenced
by Search engines like Google. The reason is that
http://fileexchange.scilab.org/robots.txt
is presently set to

User-agent: *
Allow: /index.cgi
Disallow: /

where / disallows all pages -- included the portal --
to be referenced, and where /index.cgi  does not exists
and returns a 404 error.

The situation is the same for the ATOMS's portal for external
modules: http://atoms.scilab.org/robots.txt

User-agent: *
Allow: /index.cgi
Disallow: /

whereas the bug
http://bugzilla.scilab.org/show_bug.cgi?id=10896
also prevents the Scilab ATOMS interface to propose many
available resources.

For my part, i do not see any interest in going on
uploading resources that i want to share if it is on
a site that hides them from Search engines robots.
These ones should be able to scan and refer to all
pages of these resources.
Otherwise, it would be easy and more consistent to
upload resources elsewhere and just to set on fileexchange
a pointer to them.

Hoping to read other scilab users about that (since
other potential users cannot be reached and polled ;)

Best regards
Samuel Gougeon

--
To unsubscribe from this mailing-list, please send an empty mail to
[hidden email]
To check the archives of this mailing list, see
http://mailinglists.scilab.org/

Adrien Vogt-Schilb Adrien Vogt-Schilb
Reply | Threaded
Open this post in threaded view
|

Re: Fileexchange & Atoms resources hidden to Open Search engines

Hi

For the record, I agree.

As a file user (not sharer), i find it very unpractical not being able to reach something on atoms or fileexchange just by typing the name on google.

Just an example: http://www.google.com/search?q=atoms+scilab+mingw&hl=en   How could this search not return http://atoms.scilab.org/toolboxes/mingw/ ?

I actually spend part of my time showing my colleagues where to get mingw for scilab. I would really prefer google to do it for me.

Best regards


On 16/04/2012 15:57, [hidden email] wrote:
Hello,

Beeing a sharer on Scilab Filexchange, i was wondering 
about why resources uploaded there are not referenced
by Search engines like Google. The reason is that
http://fileexchange.scilab.org/robots.txt
is presently set to

User-agent: *
Allow: /index.cgi
Disallow: /

where / disallows all pages -- included the portal -- 
to be referenced, and where /index.cgi  does not exists
and returns a 404 error.

The situation is the same for the ATOMS's portal for external 
modules: http://atoms.scilab.org/robots.txt

User-agent: *
Allow: /index.cgi
Disallow: /

whereas the bug 
http://bugzilla.scilab.org/show_bug.cgi?id=10896
also prevents the Scilab ATOMS interface to propose many
available resources.

For my part, i do not see any interest in going on
uploading resources that i want to share if it is on
a site that hides them from Search engines robots.
These ones should be able to scan and refer to all 
pages of these resources.
Otherwise, it would be easy and more consistent to
upload resources elsewhere and just to set on fileexchange
a pointer to them.

Hoping to read other scilab users about that (since 
other potential users cannot be reached and polled ;)

Best regards
Samuel Gougeon

--
To unsubscribe from this mailing-list, please send an empty mail to
[hidden email]
To check the archives of this mailing list, see
http://mailinglists.scilab.org/

gareste gareste
Reply | Threaded
Open this post in threaded view
|

Re: Fileexchange & Atoms resources hidden to Open Search engines

Hi,

This comes from a misconfiguration from our part, and was not an intended behavior. I'll change this as soon as possible.
I don't understand which flag are you talking about on ATOMS, could you be more specific? I will add a note on the website to indicate that windows modules need to be in a different version if we want to make them available for the 5.4 : we do not currently have a way on atoms to have both a <5.4 and 5.4 valid compiled module on the same version of the module.

Simon

On 04/16/2012 04:09 PM, Adrien Vogt-Schilb wrote:
Hi

For the record, I agree.

As a file user (not sharer), i find it very unpractical not being able to reach something on atoms or fileexchange just by typing the name on google.

Just an example: http://www.google.com/search?q=atoms+scilab+mingw&hl=en   How could this search not return http://atoms.scilab.org/toolboxes/mingw/ ?

I actually spend part of my time showing my colleagues where to get mingw for scilab. I would really prefer google to do it for me.

Best regards


On 16/04/2012 15:57, [hidden email] wrote:
Hello,

Beeing a sharer on Scilab Filexchange, i was wondering 
about why resources uploaded there are not referenced
by Search engines like Google. The reason is that
http://fileexchange.scilab.org/robots.txt
is presently set to

User-agent: *
Allow: /index.cgi
Disallow: /

where / disallows all pages -- included the portal -- 
to be referenced, and where /index.cgi  does not exists
and returns a 404 error.

The situation is the same for the ATOMS's portal for external 
modules: http://atoms.scilab.org/robots.txt

User-agent: *
Allow: /index.cgi
Disallow: /

whereas the bug 
http://bugzilla.scilab.org/show_bug.cgi?id=10896
also prevents the Scilab ATOMS interface to propose many
available resources.

For my part, i do not see any interest in going on
uploading resources that i want to share if it is on
a site that hides them from Search engines robots.
These ones should be able to scan and refer to all 
pages of these resources.
Otherwise, it would be easy and more consistent to
upload resources elsewhere and just to set on fileexchange
a pointer to them.

Hoping to read other scilab users about that (since 
other potential users cannot be reached and polled ;)

Best regards
Samuel Gougeon

--
To unsubscribe from this mailing-list, please send an empty mail to
[hidden email]
To check the archives of this mailing list, see
http://mailinglists.scilab.org/


-- 
--
Simon Gareste
Support  & Development Engineer
Consortium Scilab-DIGITEO
Adrien Vogt-Schilb Adrien Vogt-Schilb
Reply | Threaded
Open this post in threaded view
|

Re: Fileexchange & Atoms resources hidden to Open Search engines

On 16/04/2012 17:50, Simon GARESTE wrote:
I don't understand which flag are you talking about on ATOMS, could you be more specific? I will add a note on the website to indicate that windows modules need to be in a different version if we want to make them available for the 5.4 : we do not currently have a way on atoms to have both a <5.4 and 5.4 valid compiled module on the same version of the module.

Simon
Are you asking me? i am ot sure i understood the question. As far as i am concerned, my only problem was the lack of indexing by search engines. The problem i pointed out was an illustration (if one does not reach the atoms web page through google, he likely does not reach the page at tall and does not get the information that he needs a particular mingw distribution)

Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Re: Fileexchange & Atoms resources hidden to Open Search engines

In reply to this post by gareste
Hello Simon,

Le 16/04/2012 17:50, Simon GARESTE a écrit :
Hi,

This comes from a misconfiguration from our part, and was not an intended behavior. I'll change this as soon as possible.
I don't understand which flag are you talking about on ATOMS, could you be more specific? I will add a note on the website to indicate that windows modules need to be in a different version if we want to make them available for the 5.4 : we do not currently have a way on atoms to have both a <5.4 and 5.4 valid compiled module on the same version of the module.
About what i call "the flag": The script run by the ATOMS's server
to build the list of modules that will be listed by the ATOMS's interface
under Scilab, declares some modules in the built, and skips other ones
(that then are not proposed through the GUI). The criterium according
to which a module is "exported" for the GUI or conversely is not exported,
is not clear, and is not published. I am calling it "the flag". It is likely
a mixed condition. No-one but you may have access to it.

I'm sorry, i do not understand the last part of your answer. Some modules
-- like the Socket one -- with only macros (+ a jar for help pages.
Is building them the issue? Installation by hand works with Scilab 5.4...)
and that can run "as is" with Scilab 5.4 as they already do with Scilab 5.3 --
are not exported to the zip and therefore are not listed by the GUI.

Samuel