Defect #721

Stereotype "geographic extent"

Added by Mérour Xavier over 5 years ago. Updated about 4 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:CATALOG
Target version:4.2.0
Affected version:4.0.0

Description

The new version of easySDI (V4.x) integrates different types of stereotypes to help to edit metadata. One if "geographicextent" which existed already in V2 but has not yet been totally coded in V4.

What is missing ?

- the capability to choose multiple extents (perimeters) from a list to fill a single list of "selected perimeters" (without adding new occurences in the MD edition form, as it works now)
- the geographicIdentifiers (ISO) of the perimeters (stored in predefined perimeters) is not saved in metadata

This should be added to cover the same functionnality as available in V2.

See in attachement screenshot of what is available in V2 (GUI could be enhanced, see proposal below)


Open questions :

- in V2, there was only one stereotype with options. Should we do like this again or code another stereotype something like "geographicExtent_multiple" ?
- GUI was not perfect in V2 for searching predefined perimeters in the list). See in attchement our proposal to have a more "user-friendly" form (mainly, it adds a search on the multiselect as proposed in JUI since Joomla! v3). See proposal animated in GIF attached.

etendues_anim.gif (23.1 KB) Mérour Xavier, 05/27/2014 04:28 PM

Associated revisions

Revision 7249
Added by Battaglia Marc about 5 years ago

Issue #10556, #721, #10540, #10349
From Marc

Revision 7278
Added by Battaglia Marc about 5 years ago

Merged revision(s) 7249-7273 from branches/4.2.x:
Issue #10556, #721, #10540, #10349
From Marc
........
rollback 7232
........

Revision 7287
Added by Villemagne Jérôme about 5 years ago

Merged revision(s) 7230-7273 from branches/4.3.x:
Auto Commit from continuous integration. (easySDI_4.2.x:165 http://localhost:8080/jenkins/job/easySDI_4.2.x/165/)
........
Issues: #670, #790, #793, #794, #799, #803, #787 (partial) + missing index.html in components
From Yves
........
Auto Commit from continuous integration. (easySDI_4.2.x:167 http://localhost:8080/jenkins/job/easySDI_4.2.x/167/)
........
Auto Commit from continuous integration. (easySDI_4.2.x:168 http://localhost:8080/jenkins/job/easySDI_4.2.x/168/)
........
Migration to Boundless SDK GXP 4.1
........
[jvi - Refs #10205]:
- add an order validation process
........
Reimport correct commit from jvi r7211
........
Issue #10556, #721, #10540, #10349
From Marc
........
rollback 7232
........

Revision 7289
Added by Battaglia Marc about 5 years ago

Merged revision(s) 7249-7273 from branches/4.2.x:
Issue #10556, #721, #10540, #10349
From Marc
........
Issue #10540 Deuxième correction
........
Backup 28.08.2014
........
Backup 29.08.2014
........
Backup 01.09.2014
........
Issue #10501
........
rollback 7232
........

History

#1 Updated by Mérour Xavier over 5 years ago

@Bruno @Thomas @Jérôme

Any input on open questions ?

#2 Updated by Mérour Xavier over 5 years ago

  • Assignee set to Magoni Bruno

#3 Updated by Magoni Bruno over 5 years ago

  • Tracker changed from Feature to Defect
  • Status changed from New to Affected
  • Assignee changed from Magoni Bruno to Battaglia Marc
  • Affected version set to 4.0.0

#4 Updated by Blatti Yves over 5 years ago

After phone call with Marc and discussion at ASIT VD, we all agreed on a simplified version of this stereotype:
It will be a simple multiselect with choosen, plus customization:
  • as in v2, items label will contain their type (ex: "Bex [Commune VD]")
  • items will stack vertically (all the same size)
  • container will have a max height (because we can have hundreds of items selected see here)
  • selected items will be alphabetically sorted (on opening , and when adding new ones)
  • initial size of select is standard (see here)
  • selected items are visible in the dropdown but disabled (see here)
  • not visible here, but we'd like that the placeholder remains visible even if some values are selected

Sample fiddles:

(blank select, like in a new MD)
http://jsfiddle.net/M7Td2/

(preselected values, linke a metadata update)
http://jsfiddle.net/K6U4C/

#5 Updated by Battaglia Marc over 5 years ago

  • Status changed from Affected to Resolved
  • % Done changed from 0 to 100

#6 Updated by Magoni Bruno over 5 years ago

  • Status changed from Resolved to Closed
  • Assignee changed from Battaglia Marc to Mérour Xavier
  • Affected version changed from 4.0.0 to

#7 Updated by Magoni Bruno over 5 years ago

  • Status changed from Closed to New
  • Assignee changed from Mérour Xavier to Magoni Bruno

Need some explanations as feature haven't been developed as initially mentioned...

#8 Updated by Magoni Bruno over 5 years ago

  • Status changed from New to Affected
  • Assignee changed from Magoni Bruno to Blatti Yves

Hi Yves,

If I understand well, could you please summarize what needs to be done for finalizing issue as initially described, or keep we such integration as is ?

Thanks in advance,
Bruno

#9 Updated by Blatti Yves over 5 years ago

  • Assignee changed from Blatti Yves to Magoni Bruno
Remain points:
  • items will stack vertically (all the same size)
  • container will have a max height (because we can have hundreds of items selected)
  • initial size of select is standard
  • we'd like that the placeholder remains visible even if some values are selected

Problem is, we use joomla default chosen, and it doesn't inherit classes from original select.
So we can't add CSS and js on an object we don't know.
We'll have to find a trick for this.

Marc told me that he doesn't have time for this feature anymore. So we can give it a try at ASIT VD.

What do you think ?

#10 Updated by Magoni Bruno over 5 years ago

  • Assignee changed from Magoni Bruno to Blatti Yves
  • Affected version changed from to

If you want to take time about ergonomic remaining points, I don't see any problem.
But it is important to locate these ergonomic features outside of this ticket if you have not time to work quickly on it (next 2 weeks).
I guess it's time to stop adding new features to 4.2 version as it's important now to have a stable version regarding to the milestones delivery...

So, I let you creating a new issue for such remaining points regarding your availability; in this case such ticket can be affected back to me and I will state it as "resolved"...

Thanks,

#11 Updated by Magoni Bruno over 5 years ago

  • Target version changed from Unplanned to 156
  • Affected version changed from to 4.0.0

#12 Updated by Blatti Yves over 5 years ago

  • Assignee changed from Blatti Yves to Magoni Bruno

OK, so I propose to only add a class to these items so we can "play" with their look in CSS (in our template).
Something like this (I can push it on my next commit):

$jfield->__set('class','sdi-extent-multiselect');

And we'll fill a ticket if we need more, or if we produce something generic enough for the community.

Would it be OK?

#13 Updated by Blatti Yves over 5 years ago

Ho, it didn't hit me in the first place, but labels are wrong, the type is missing.
We have "Bex" instead of "Bex [Commune VD]"

#14 Updated by Magoni Bruno over 5 years ago

  • Assignee changed from Magoni Bruno to Battaglia Marc

#15 Updated by Battaglia Marc about 5 years ago

  • Status changed from Affected to Resolved
  • Assignee changed from Battaglia Marc to Blatti Yves

Thank you to test on your environment.

#16 Updated by Blatti Yves about 5 years ago

Hi, I'm on holidays for now, I'll check when I'll be back.

The remains point before I left were:
  • note13 (the category(type) is missing)
  • #796 (Stereotype geographic extent stores database ids intestead of "codes")

I'll give you inputs afters tests on Monday !

#17 Updated by Magoni Bruno about 5 years ago

  • Target version changed from 156 to 157

#18 Updated by Van Hoecke Hélène about 5 years ago

  • Assignee changed from Blatti Yves to Van Hoecke Hélène

#19 Updated by Van Hoecke Hélène about 5 years ago

  • Status changed from Resolved to Closed

#20 Updated by Magoni Bruno almost 5 years ago

  • Target version changed from 157 to 4.2.0

#21 Updated by Van Hoecke Hélène about 4 years ago

  • Assignee deleted (Van Hoecke Hélène )

Also available in: Atom PDF