-
Notifications
You must be signed in to change notification settings - Fork 5
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
Editor App #17
Comments
Problem is back. I think I understand what is happening but not how to fix. We default to the alphabetical order. |
I think collatex returns the data in alphabetical order nonetheless. I wrote code to re-order the table and that's probably not doing what it should. See lines 57-70. We can look at it together tomorrow |
Yes, let's. I could not figure out how to get the initial request list back
to the js.
…------------------------------
Robert H. Smith Professor of Jewish Studies and
Professor of History
Department of History
University of Maryland
2115 Francis Scott Key Hall
College Park, MD 20742
301 405 4296 | [email protected]
www.digitalmishnah.org | www.eRabbinica.org
Director
Joseph and Rebecca Meyerhoff
Program and Center forJewish Studies
University of Maryland
4141 Susquehanna Hall
College Park, MD 20742
301 405 4975 | [email protected]
www.jewishstudies.umd.edu
------------------------------
On Tue, Apr 10, 2018 at 4:56 PM, Raffaele Viglianti < ***@***.***> wrote:
I think collatex returns the data in alphabetical order nonetheless. I
wrote code to re-order the table and that's probably not doing what it
should. See lines 57-70
<https://github.com/umd-mith/mishnah/blob/exist/resources/editapp/mishnaControllers.js#L57>.
We can look at it together tomorrow
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABBRzeAgo0SsTfPRRQHuJPgOH5oXEUqFks5tnRyCgaJpZM4S3cOa>
.
|
I think I figured out what is going on.
passThru.xql serialized as json I changed this (following your earlier
module, getTknsJson.xql) to
declare option output:method "text";
declare option output:media-type "text/javascript";
This seems to work, and does not affect the functioning of calls on the
function from within exist.
…------------------------------
Robert H. Smith Professor of Jewish Studies and
Professor of History
Department of History
University of Maryland
2115 Francis Scott Key Hall
College Park, MD 20742
301 405 4296 | [email protected]
www.digitalmishnah.org | www.eRabbinica.org
Director
Joseph and Rebecca Meyerhoff
Program and Center forJewish Studies
University of Maryland
4141 Susquehanna Hall
College Park, MD 20742
301 405 4975 | [email protected]
www.jewishstudies.umd.edu
------------------------------
On Tue, Apr 10, 2018 at 4:56 PM, Raffaele Viglianti < ***@***.***> wrote:
I think collatex returns the data in alphabetical order nonetheless. I
wrote code to re-order the table and that's probably not doing what it
should. See lines 57-70
<https://github.com/umd-mith/mishnah/blob/exist/resources/editapp/mishnaControllers.js#L57>.
We can look at it together tomorrow
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABBRzeAgo0SsTfPRRQHuJPgOH5oXEUqFks5tnRyCgaJpZM4S3cOa>
.
|
What if the xquery that generates the json for collatex actually returns an array:
Then we don't have to iterate through the json to extract order. |
Another, even simpler possibility:
The data automatically comes back sorted by query order. |
@raffazizzi : Made minimal modifications to mishnahControllers.js and compare.xql to account for this. |
Editor app sorting not working properly
Sorting by input data does not work properly. Sorts the row headers but not the data. In the screenshot below, S00483 has the token "TEST" at the beginning of the target
<ab>
and it still appears where the alphabetically sorted tokens would be (i.e., P00001, P00002, S00483, ...), but the row headers reflects the query order (S00483 first)The text was updated successfully, but these errors were encountered: