no Tags records in some info-files

[AbNoRMiS]

these info-files have no Tags records

bluefish-doc.tcz.info
bluefish-locale.tcz.info
bluefish.tcz.info
garcon-dev.tcz.info
garcon-doc.tcz.info
garcon-locale.tcz.info
garcon.tcz.info
gstreamer-dev.tcz.info
gstreamer-locale.tcz.info
gstreamer.tcz.info
inflator.tcz.info
install-citrix-receiver.tcz.info
libgmtk-dev.tcz.info
libgmtk-locale.tcz.info
libgmtk.tcz.info
pcmanfm-mod-locale.tcz.info
pcmanfm-mod.tcz.info
perl_Digest_Whirlpool.tcz.info
reaver.tcz.info
seamonkey.tcz.info
wmii-dev.tcz.info
wmii-doc.tcz.info
wmii.tcz.info

therefore these extensions can not be found through the appbrowser
despite the fact that the appbrowser has three search methods
except search by tags there are two search ways but it no give results

[AbNoRMiS]

gstreamer.tcz.info
seamonkey.tcz.info

was corrected

but there were new info-files without tags

python-dev.tcz.info
python.tcz.info

[Rich]

Hi AbNoRMiS
Recently roberts ran a script against all the extensions in the repository to add a Tags field to any info file which
did not have one. This does not however guard against newly or resubmitted extensions whose info file is once
again missing that field. Maybe that script should be run against all incoming extensions to force them into
compliance if they don't contain a tags field.

[AbNoRMiS]

yes, i saw that roberts ran this script
when updated core 4.3 to 4.4
i think that should add it run from the main script
that updates repository database every 5 hours

[Jason W]

Python info files fixed.

[AbNoRMiS]

yes, i saw that roberts ran this script
when updated core 4.3 to 4.4
i think that should add it run from the main script
that updates repository database every 5 hours

and apply it only to latest updated or added extensions to avoid excessive server workload

[Jason W]

I think I added a Tags check in the submitqc4 extension, I used my previous info files on my HD and had not updated my build host's submitqc4 when I updated python. 

What can be done to not have to have a cron job on the server for the Tag field is to have a fallback Tags addition like was done initally as part of the submitqc4.  That way, no Tag field, and a default based on the desctription is inserted into the info files being checked. 

[roberts]

I was initially using the Desc field for keywords and that was not good enough, claimed the community.
So I jump started the Tags by batch processing all extensions with a script to filter out common words to make auto tag items.

The only way for Tag items to show up missing is because of an update to the extension. Therefore, the extension maker should be contacted to correct this error. It is likely that their local copy of the .info is missing the Tags field. If it is not corrected by the extension maker, i.e., update his local .info, then the tag will come up missing on the next submitted update.

If we have to "fall back" to "inserting" the Desc to Tags, then that defeats the purpose as the Desc field was, and still is, not good enough.

[Jason W]

After more thought, I agree, that a missing Tags field be fixed on a case by case basis.  The audit script checks for them and echoes a warning if not found.  The actual fixing should be done by the extension maker.  Hopefully in time a forgotten Tags field will be rare.

[AbNoRMiS]

If we have to "fall back" to "inserting" the Desc to Tags, then that defeats the purpose as the Desc field was, and still is, not good enough.

possible need inserting field title as a keyword
then extension will get to search results by name

[Rich]

Hi AbNoRMiS
The Tags field is required and should be properly filled out just like all the other fields.

[AbNoRMiS]

i meant a little other
regarding search by fields tags and title
i.e. inserting title to tags field when searching
instead inserting description

[roberts]

Please contact the respective extension maker so that they can correct their extensions.

[AbNoRMiS]

okay i'll do it

[hiro]

Sorry, only now I came to see that private message, but I don't feel like I'm the right guy to do it. Because of technical issues I'm still using 3.x and can't test my extensions on 4.x. Everything from kernel to userland is evolving a bit too fast for me to possibly keep up with in my freetime, so if there is any 4.x related problem anybody who feels the need please just go ahead and change or resubmit the extension.

If there is a problem with an extension itself or an update request I'm still there of course