if I have many survey. It very hard to find the survey for user.
can LimeSurvey had any page for user input only survey id and redirect to the survey that user want or input.

No, you will need to code a custom page to do the redirect.

Thanks, tpartner

Maybe some "javascript" filter can be done in "Survey list page". I already done a template system for big list in survey (must make a plugin and publish ...).

Idea:
- Add a "text input" above survey list
- When user enter some string in this input : the survey list is filtered by this input (surveyid and surveyName)


Denis
PS : have the idea, but no time to develop currently

I develop it on my sever
e-survey.oarit.rmuti.ac.th
by config Webserver call index.html and when user enter survey id it will redirect to e-survey.oarit.rmuti.ac.th/index.php/surveyid?lang=th .

But I think if it's on the first page or as a plugin to display the first page would be better.

any comments?

You can update surveylist.pstpl,

Quick idea :
- Make a copy of your template
- Set this copy to "default" template
- put in github.com/LimeSurvey/LimeSurvey/blob/ma...ews/surveylist.pstpl in place of {SITELOGO}/{SITENAME} for example something like this:
After : maybe you can control if surveyid is in list of survey in javascript.

Denis

Thank you, Denis.

This request is related to this one:
www.limesurvey.org/forum/can-i-do-this-w...i-categorise-surveys

I think we should add the tag system for LS3, it's pretty easy to implement.

LouisGac Tag is a group of the survey right ?, but survey id is not specific to the survey. I think that kind of thing.

No, a tag is just a tag: a list of strings separated by a comma: so just a new field in the DB for the survey table. Surveys have tags: you can add or remove a tag to a survey, and you can make an union of all the surveys having this or this tag. So you can "group" surveys by union: all the surveys having the same tag... But there is nothing like an entity "group".

A real "group" is different: a group is a relation: at least two new tables in the DB, one table for the groups (group name, description, etc), and then another table for the relation (this survey belong to this group). Groups have surveys, you can add or remove a survey to a group, then you can show all the surveys belonging to a group. But in general, the reason why you use a new entity like a "group" is not only to filter items, it's rather to create an advanced permission system . Group of users ("roles") can do things with a group of items ("categories"). Eg: Users with role "student" can edit any survey in category "university" but can't edit survey in category "laboratory".

Implementing an ACL system inside LimeSurvey is a long term goal, because it would imply to rewrite the existing permission system.

But the tag system, that could be done quite quickly.

Thanks for Knowledge It is hoped that the concept of the SurveyID will be developed too.