Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regional fact sheets are not connected with time slider #129

Open
tdipisa opened this issue Oct 30, 2014 · 7 comments
Open

Regional fact sheets are not connected with time slider #129

tdipisa opened this issue Oct 30, 2014 · 7 comments
Assignees

Comments

@tdipisa
Copy link
Member

tdipisa commented Oct 30, 2014

The year inside the regional fact sheet should be aligned to the selected year into the MapViewer

@tdipisa tdipisa self-assigned this Oct 30, 2014
@tdipisa
Copy link
Member Author

tdipisa commented Oct 30, 2014

I think this is an update for the XSL code that manages these fact sheets. inside the VME-DB we use directly the URL provided by the REST service in order to instantiate an Iframe. We follow the same behavior for the other non-regional factsheets without specifying the year explicitly (in these fact sheets the year's dropdown on top is aligned automatically).

@fabio2111
Copy link

Please provide information about who is going to work on this

@tdipisa
Copy link
Member Author

tdipisa commented Nov 7, 2014

I dont know exactly who manages the xsl files, maybe Marco Balestra?

@fabio2111
Copy link

Is Marco receiving these tickets?

@eblondel
Copy link

eblondel commented Nov 7, 2014

He's not. AFAIK, he has to be on Github and "watch" the VME-viewer
repository, otherwise he's not notified.

Le 07/11/2014 11:44, fabio2111 a écrit :

Is Marco receiving these tickets?


Reply to this email directly or view it on GitHub
#129 (comment).

@fabio2111
Copy link

Have you enabled Marco to "watch" this VME-Viewer GitHUB or invited him to do so? Who has to act on this? Thanks

@tdipisa
Copy link
Member Author

tdipisa commented Nov 13, 2014

I've already sent an email on the mailing list some days ago, with the same subject of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants