Giter VIP home page Giter VIP logo

navigator's Introduction

Overview

The applications in this directory all concern storage of and access to papyri.info records; that is to say, their purpose is persistence, retrieval, and display rather than editing or creation of new texts, and they thus relate chiefly to the papyri.info navigator rather than the editor.

In broad outline, the packages below have the following tasks:

  1. pn-dispatcher - Java servlets for persistence, retrieval, and display of
    papyri.info records once processed by pn-indexer, pn-mapping, pn-lemmas, pn-solr, and pn-xslt files. Three servlets are contained here:
  2. info.papyri.dispatch.browse.CollectionBrowser - for browsing by collection name
  3. info.papyri.dispatch.browse.facet.FacetBrowser - for faceted browse and search using a variety of criteria
  4. info.papyri.dispatch.atom - outputs an atom feed summarising texts, limitable by edit date
  5. pn-indexer - Collates XML files using information from the Numbers Server
    and feeds information drawn from them into the Solr index
  6. pn-lemmas - Adds lemmatisation information to the Solr index
  7. pn-mapping - parses the XML files in order to resolve identifiers and retrieve collation and collection information; stores the result as triples in the Numbers Server.
  8. pn-site - HTML, JS, CSS, and img files for the Navigator site
  9. pn-solr - config and other required files for the Solr index
  10. pn-sync - synchronises the contents of the numbers server and Solr index with the contents of the 'mothership' repository (i.e., publishes texts entered via the editor to the navigator)
  11. pn-xslt - XSLT stylesheets used for HTML display and Solr indexing.

Environment

As the above implies, three components are required for the Navigator to function.

  1. A servlet container, such as Tomcat, for the Java servlets
  2. A Numbers Server, for storing RDF information correlating the various files
  3. A Solr server, for search functionality.

A sample script for appropriately starting/stopping these three components - dlib_tomcat_pi - is provided. This script should give you most of the information you need.

Note that in this script, stoptc and starttc both refer to stopping/starting the editor. To stop and start the navigator and associated services, use startsolr and stopsolr.

Certain apache settings - in particular rewrite rules - are fundamental to the correct application function. These are given in the pi.conf file.

The Servlet container

The servlet container used is Tomcat 7.0.16, with the servlets being deployed in the webapps directory as a .war file (dispatch.war).

Note the additional memory allocation here, with JAVA_OPTS settings at -Xms768m -Xmx768m -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+CMSClassUnloadingEnabled. This is largely necessitated by the performance demands of the Solr indexing process.

Even more importantly, note that the location of the solr.solr.home variable is set in JAVA_OPTS (normally solr.solr.home=/data/papyri.info/solr). This location is not the default location, and without explicit setting of the solr home, servlets will be unable to locate the Solr index.

The pi.conf file assumes that Tomcat will be running on port 8083.

The Numbers Server

The numbers server triple store is Jena-Fuseki 0.2.2. It is assumed to be available on port 8090.

The Solr Server

As noted above, Solr home is assumed to be located at /srv/data/papyri.info/solr. With the exception of the data directory, this directory should contain the files and structure given in pn-solr, or simply symlinks to these.

Because Solr runs in the same webapps directory as dispatch.war, it will also be available over port 8083.

Note that the Solr deployment is multicore, with cores pn-search and pn-search-offline. Indexing is done into pn-search-offline, which is then swapped for the pn-search core to bring the newly created index online.

Directory Structure

The directory structure is expected to conform to:

/srv/data/papyri.info/solr - for Solr home
/srv/data/papyri.info/jena - for numbers server data storage
/srv/data/papyri.info/git/navigator - holding the gthub-synchronised application files themselves
/srv/data/papyri.info/idp.data - IDP XML files (the 'mothership' repository), as given at https://github.com/papyri/idp.data
/srv/data/papyri.info/pn/idp.html - the IDP HTML files generated from the files in /data/papyri.info/idp.data
/srv/data.papyri.info/pn/home - the HTML, CSS, JS, and image files used throughout the site and in interactive interfaces. This directory can consist simply of a symlink to /srv/data/papyri.info/git/navigator/pn-site.

Adapting to a different directory structure is straightforward, but will mean finding where there are hard-coded directory locations and changing them.

Building and Running

Java servlets are built using Maven 3.0.3. Once Maven is installed, dependency calculation and download should proceed automatically - though note in particular the existence of the project's Maven repo at http://dev.papyri.info/maven/.

Applications written in Clojure (pn-mapping, pn-indexer, and pn-lemmas) will require leiningen - which is itself Maven-based.

navigator's People

Contributors

hcayless avatar t-hill avatar paregorios avatar ryanfb avatar wsalesky avatar m-k-r avatar cgajjar05 avatar leoba avatar dependabot[bot] avatar jcowey avatar gajjar05 avatar samosafuz avatar gabrielbodard avatar

Stargazers

Régis Robineau avatar Marius Jøhndal avatar Mike Slattery avatar A.G. avatar Jaimie Murdock avatar  avatar  avatar

Watchers

 avatar  avatar Elemmire avatar  avatar Bridget Almas avatar  avatar James Cloos avatar A.G. avatar Daniel Riaño avatar  avatar

navigator's Issues

Numbering in Arabic only texts

Would you please merge from papyri.info to dev.papyri.info to include this text (Arabic only), which I have just added to papyri.info

http://papyri.info/ddbdp/p.worp;;65

could you please display the line numbers as in the edition, which you will find in .doc form here:

http://147.142.225.252/Xcoded/PWorp/Text%2065def.doc

i.e. Arabic numbers without a dot (neither before nor after the numeral)

and running RTL

and as in the rest of papyri.info in fives (5, 10, 15, 20 etc)

This seems to be relatively standard practice in modern Arabic editions. I have spoken to Lajos and Usama who were alright with this. (Not to say that others will be. There will almost certainly be others who do not like it, but it would be something to show)

Changing dclp-hybrid "na"

Simply to make an issue for this, even if we have to step back from it.

It would be great to get rid of the "na" in DCLP files. Here is an example:

https://github.com/papyri/idp.data/blob/master/DCLP/69/68357.xml#L15

<idno type="dclp-hybrid">na;;68357</idno>

This should (in a better world) be

<idno type="dclp-hybrid">tm;;68357</idno>

After all it is a tm number and should be called such (a litpap.info aberration, sorry!). Users would be able to understand it etc. etc.

Obviously editor knock on effects will have to be considered.

Instate new Series Names and Reindex

The following new series were added (relatively) recently to collection.rdf
https://github.com/papyri/idp.data/blob/master/RDF/collection.rdf#L1281-L1314

On http://papyri.info/browse/hgv/
P.Ryl.Copt. is displayed
O.Frange is displayed
P.Monts.Roca is displayed
P.Turku is displayed
P.Aktenbuch is displayed

P.Cair.Preis.2 is NOT displayed
on analogy with P.Gen. possibly does not have to show separately as all texts are reedited
P.Stras.Copt. is NOT displayed
Short Texts is NOT displayed
T.BM Arlt is NOT displayed
P.KRU is NOT displayed
ZPE is NOT displayed

On http://papyri.info/browse/ddbdp/

http://papyri.info/ddbdp/p.ryl.copt is displayed
http://papyri.info/ddbdp/o.frange is displayed

http://papyri.info/ddbdp/p.cair.preis.2 is NOT displayed is not on tree (https://github.com/papyri/idp.data/tree/master/DDB_EpiDoc_XML)
needs to be treated analogously to
https://github.com/papyri/idp.data/tree/master/DDB_EpiDoc_XML/p.gen.2/p.gen.2.1
https://github.com/papyri/idp.data/tree/master/DDB_EpiDoc_XML/p.cair.preis.2/p.cair.preis.2.1
http://papyri.info/ddbdp/p.monts.roca is NOT displayed is on tree
https://github.com/papyri/idp.data/tree/master/DDB_EpiDoc_XML/p.monts.roca/p.monts.roca.4
http://papyri.info/ddbdp/p.turku is NOT displayed is not on tree
http://papyri.info/ddbdp/p.aktenbuch is NOT displayed is on tree
https://github.com/papyri/idp.data/tree/master/DDB_EpiDoc_XML/p.aktenbuch
http://papyri.info/ddbdp/p.stras.copt is NOT displayed is not on tree
http://papyri.info/ddbdp/short.texts is NOT displayed is not on tree
http://papyri.info/ddbdp/t.bm.arlt is NOT displayed is not on tree
http://papyri.info/ddbdp/p.kru is NOT displayed is on tree
https://github.com/papyri/idp.data/tree/master/DDB_EpiDoc_XML/p.kru
http://papyri.info/ddbdp/zpe is NOT displayed is not on tree

Would you, please, do a reindex and make sure that all the files that are not at present displayed are all visible in the relevant places. Many thanks.

Reindex please

Hello, Hugh, may I please ask you to do a re-index of all ddb and hgv files this weekend.

Heid.Arab

Hugh, would it be possible for you to fix the following quickly (or does it need a full re-index)?
This weekend I created a new series: p.heid.arab
papyri/idp.data@25caeb1
With this i renamed two files
https://github.com/papyri/idp.data/blob/master/DDB_EpiDoc_XML/p.heid.arab/p.heid.arab.1/p.heid.arab.1.1.xml
and
https://github.com/papyri/idp.data/blob/master/DDB_EpiDoc_XML/p.heid.arab/p.heid.arab.1/p.heid.arab.1.3.xml
with there respective metadata files
https://github.com/papyri/idp.data/blob/master/HGV_meta_EpiDoc/HGV46/45353.xml
and
https://github.com/papyri/idp.data/blob/master/HGV_meta_EpiDoc/HGV107/106482.xml

Now
http://papyri.info/hgv/45353
and
http://papyri.info/hgv/106482
display nicely, but without relevant Arabic text.
http://papyri.info/ddbdp/p.heid.arab;1;1
and
http://papyri.info/ddbdp/p.heid.arab;1;3
return

HTTP Status 404 -
type Status report
message
description The requested resource () is not available.
Apache Tomcat/7.0.16

It would be really great to have this showing today if possible. Would facilitate working with Andreas Kaplony towards getting Arabic into papyri.info.

stud.pal;5;119 not loadable

Provide new URLs for link to source for HGV

When the Navigator displays the aggregated Metadata and Text files, there is a link to the source of the Metadata (i.e. Link back to HGV). E.g. go to
http://papyri.info/ddbdp/bgu;6;1215
one sees
BGU 6 1215 [source] [xml]
when one clicks [source] it goes to
http://aquila.papy.uni-heidelberg.de/Hauptregister/FMPro?-db=hauptregister_&TM_Nr.=7306&-format=DTableVw.htm&-lay=Liste&-find
where TM_Nr.=7306, was how this was built
It should now go to
http://aquila.zaw.uni-heidelberg.de/hgv/7306
This is built analogously to when on clicks on [xml]
http://papyri.info/hgv/7306/source

Sync enhancements

When you are working on getting sync to work in the new environment with ddb, hgv and the new dclp stuff, please check that biblio is also being updated.
So far biblio is only fully up-to-date after a complete re-index.

Fix sync please

Since Monday of this week sync has choked

{
  "success": true,
  "status": "Syncing files."
  "started": "Mon Oct 17 11:23:05 EDT 2016"
  "last": "Mon Oct 17 11:23:05 EDT 2016"
}

Would you please fix and reboot or whatever you have to do to make it all work again properly.
Thanks

DCLP Results Discrepancies

There's a large discrepancy in the PN between the number of DCLP records appearing under Collection in litpap and those in papyri.info. The former shows 14636 (see here) and the latter 10211 (see here) records; you’ll notice that the first 4 hits on the litpap page are absent from the papyinfo page. What is related, if you navigate to P.Herc. in the Series menu, you’ll find that litpap displays 232 hits (litpap p.herc.) whereas papyinfo shows 67 (http://www.papyri.info/search?DATE_MODE=LOOSE&DOCS_PER_PAGE=15&SERIES=dclp%3Ap.herc). As far as I can tell, files are not actually missing from papyri.info, they’re just not appearing in the PN.

Reindex and fix sync, please

Would you please reindex again, Hugh.
In the last three days work that has been done has not be reflected in the browse version of the texts. E.g.
https://github.com/papyri/idp.data/blob/master/DDB_EpiDoc_XML/p.cair.zen/p.cair.zen.3/p.cair.zen.3.59377.xml
was changed but is not visible in
http://papyri.info/ddbdp/p.cair.zen;3;59377

Sync also does not seem to be performing correctly. It did so briefly last week when you fixed it. It seems, however, to have struck difficulties again.

Would you please have a look and try to fix it.

Many thanks

James

p.koeln;14,584 behaving strangely

Hello, Hugh, would you please take a look at the following and see if you can fix it, or let me know what has to be done to fix it.

http://papyri.info/hgv/697591/source
works fine
http://papyri.info/hgv/697591/
produces
HTTP Status 404 -

type Status report

message

description The requested resource () is not available.
Apache Tomcat/7.0.16

The file
https://github.com/papyri/idp.data/blob/master/DDB_EpiDoc_XML/p.koeln/p.koeln.14/p.koeln.14.584.xml
looks fine to me as far as idnos is concerned
the matching file
https://github.com/papyri/idp.data/blob/master/HGV_meta_EpiDoc/HGV698/697591.xml
also looks good.

Why does
http://papyri.info/ddbdp/p.koeln;14;584
and
http://papyri.info/hgv/697591
produce

HTTP Status 404 -

type Status report

message

description The requested resource () is not available.

?? strange ??

Incomplete Search Results

Reindex please

Hello Hugh. Please do a reindex of idp.data.
Would you please look especially at
https://github.com/papyri/idp.data/tree/master/Biblio/96
I suspect they have been missed in previous reindexing. An example:
https://github.com/papyri/idp.data/blob/master/Biblio/96/95026.xml
A search for "Spiegelberg" in
http://papyri.info/bibliosearch
offers no return. A search for "Siegesfeier" also returns nothing.
A special reindex of this folder may be necessary.

Would you also please look at #22. It would be great to have it on display.

Search API for papyri.info and Developper Guide

Hi,
First of all, thank you for opening data to github, it is a pioneering project and i really hope to see more from it. I was trying to harvest some texts from papyri.info for research purposes. I have noticed that though the xml schema definition stays the same, 8.16 epidoc, the information encoded inside the document changes place. For example, here the date of the document is under head which is a child of the body tag under the text tag, whereas in here there is no date at all in the transcription file, but the date of the document is found in another file here under origDate tag.

Is there an api where we can simply enter the terms we have used in the navigator to harvest the resulting text with the information presented in the search page: date, place, line number, etc. I have noticed that you are using SOLR, the eagle project also uses it and there there is an entry point for interacting directly with SOLR for making queries. Maybe there is something similar for papyri.info too, but i've failed to find it.
I've also noticed that the sections of the project is quite well documented, which made me wonder if there is a guide for developpers for covering simple interactions such as i've inquired.

Thanks again for the project.

Files not being displayed

None of the following lead to a display:

http://papyri.info/ddbdp/p.lips;1;34dupl
http://papyri.info/ddbdp/p.lips;1;35
http://papyri.info/ddbdp/chla;12;524

http://papyri.info/hgv/22345
http://papyri.info/hgv/22346

Here are the details

https://github.com/papyri/idp.data/blob/master/DDB_EpiDoc_XML/p.lips/p.lips.1/p.lips.1.34dupl.xml#L14-L18

    <idno type="filename">p.lips.1.34dupl</idno>
        <idno type="ddb-perseus-style">0153;1;34dupl</idno>
        <idno type="ddb-hybrid">p.lips;1;34dupl</idno>
        <idno type="HGV">22345</idno>
        <idno type="TM">22345</idno>       

https://github.com/papyri/idp.data/blob/master/DDB_EpiDoc_XML/p.lips/p.lips.1/p.lips.1.34dupl.xml#L55

        <ref n="chla;12;524" type="reprint-in">dupl=Ch.L.A. 12,524</ref>

https://github.com/papyri/idp.data/blob/master/HGV_meta_EpiDoc/HGV23/22345.xml#L10-L14

        <idno type="filename">22345</idno>
        <idno type="TM">22345</idno>
        <idno type="ddb-perseus-style">0153;1;34dupl</idno>
        <idno type="ddb-filename">p.lips.1.34dupl</idno>
        <idno type="ddb-hybrid">p.lips;1;34dupl</idno>

https://github.com/papyri/idp.data/blob/master/DDB_EpiDoc_XML/chla/chla.12/chla.12.524.xml#L14-L18

        <idno type="filename">chla.12.524</idno>
        <idno type="ddb-perseus-style">0279;12;524</idno>
        <idno type="ddb-hybrid">chla;12;524</idno>
        <idno type="HGV">22346</idno>
        <idno type="TM">22346</idno>

https://github.com/papyri/idp.data/blob/master/DDB_EpiDoc_XML/chla/chla.12/chla.12.524.xml#L61-L62

        <ref n="p.lips;1;35" type="reprint-from">P.Lips. 1,35</ref>
        <ref n="p.lips;;34dupl" type="reprint-in">dupl=P.Lips. 34dupl</ref>

https://github.com/papyri/idp.data/blob/master/DDB_EpiDoc_XML/p.lips/p.lips.1/p.lips.1.35.xml#L14-L18

        <idno type="filename">p.lips.1.35</idno>
        <idno type="ddb-perseus-style">0153;1;35</idno>
        <idno type="ddb-hybrid">p.lips;1;35</idno>
        <idno type="HGV">22346</idno>
        <idno type="TM">22346</idno>

https://github.com/papyri/idp.data/blob/master/DDB_EpiDoc_XML/p.lips/p.lips.1/p.lips.1.35.xml#L47-L50

        <ref type="reprint-from">dupl=P.Lips. 34dupl</ref>
        <ref n="chla;12;524" type="reprint-in">Ch.L.A. 12,524</ref>
     </head>
     <div xml:lang="grc" type="edition" xml:space="preserve"><ab/></div>

https://github.com/papyri/idp.data/blob/master/HGV_meta_EpiDoc/HGV23/22346.xml#L10-L14

        <idno type="filename">22346</idno>
        <idno type="TM">22346</idno>
        <idno type="ddb-perseus-style">0153;1;35</idno>
        <idno type="ddb-filename">p.lips.1.35</idno>
        <idno type="ddb-hybrid">p.lips;1;35</idno>

Merge and re-index please

Hugh,

would you please merge the following two commits into
https://github.com/papyri/idp.data/tree/master/HGV_meta_EpiDoc

they are:
papyri/idp.data@4f2476e
and
papyri/idp.data@5af8eef

found at:
https://github.com/papyri/idp.data/commits/xwalk

These provide "metadata" for P.Genova V and P.Köln XIV. Since both P.Genova and P.Köln already exist as series, a new volume should appear in
http://papyri.info/browse/hgv/PUG (P.Genova)
and
http://papyri.info/browse/hgv/P.Koln

I would assume.
Would you also do a full re-index in order to catch up with #7, because papyri.info is still linking back to an old and now defunct defunct link.

File got lost somewhere in the machinery

Hello Hugh, I had what looked like a time out on finalization. You can see the details in
papyri/sosol#31
Somehow or other this file
http://papyri.info/editor/publications/50138
has not been picked up by sync and thus not incorporated into the master files.
Would you please have a look and try to fix it in such a way to ensure the
p.cair.mich.2.12f_r.xml
is included in
https://github.com/papyri/idp.data/tree/master/DDB_EpiDoc_XML/p.cair.mich/p.cair.mich.2
and is displayed next to the metadata at
http://papyri.info/hgv/397533

Thanks

Re-index please

As of today I have managed to rename all the files which ended ...dgtl. There are all now in:
https://github.com/papyri/idp.data/tree/master/DDB_EpiDoc_XML/ddbdp
Would you please do a reindex so that all the realignment can take place and so that old alignments disappear. Only
http://papyri.info/ddbdp/ddbdp;2013;1
displays properly
http://papyri.info/ddbdp/ddbdp;2014;1
http://papyri.info/ddbdp/ddbdp;2015;1
http://papyri.info/ddbdp/ddbdp;2015;2
http://papyri.info/ddbdp/ddbdp;2015;3
all display
HTTP Status 404 -

type Status report

message

description The requested resource () is not available.
Apache Tomcat/7.0.16

p.petr;3;42 error

HGV series display not working as would be liked

Browsing by HGV
http://papyri.info/browse/hgv/
then to series and volume we get the following
http://papyri.info/search?SERIES=P.Oxy.&VOLUME=83
where only those numbers which already have a relevant ddbdp file are displayed.

Here we would like to see a list of all P.Oxy. 83 numbers for which there is no text added. This is the way most people locate files in order to add the relevant Greek / Latin / Coptic text.

Would you please make it work again in that way.

Display of "Header" in DCLP

First of all what do I mean by "Header"?
An example from existing papyri.info.
http://papyri.info/ddbdp/p.mich;8;465
The bit below the Browse (in grey) section
Bildschirmfoto 2019-04-11 um 15 38 41
that is the string
p.mich.8.465 = HGV P.Mich. 8 465 = Trismegistos 17239 = oxford-ipap.apis.1613 = michigan.apis.2580
It is, of course, the same in dev
http://dev.papyri.info/ddbdp/p.mich;8;465
That is what I am calling a "Header"

I have found one category of "Header" in dev DCLP that is at present displayed in a way that we would like to change please. Described below.

Merge and re-index please

Hugh,

would you please merge the following commits into
https://github.com/papyri/idp.data/tree/master/HGV_meta_EpiDoc

papyri/idp.data@ae81a66
and
papyri/idp.data@75aa5ec (probably not necessary as it is overwritten by the one above)
and
papyri/idp.data@9fd6264
and
papyri/idp.data@5ce0b22

found at:
https://github.com/papyri/idp.data/commits/xwalk

These provide "metadata" for O.Bankes and P.Daris, both of which are new series. Would you please make the relevant changes to
https://github.com/papyri/idp.data/blob/master/RDF/collection.rdf
as well as making them both appear at the relevant position in
http://papyri.info/browse/ddbdp/
and
http://papyri.info/browse/hgv/

Then please reindex. There seems to have been funny stuff going on today with github (is it part of the reported DDoS attacks?).
Reindex should also make p.cair.arab. appear I would hope.

Anyway that would be stupendous if you could get this done for next week.

Many thanks

Merge and re-index please

Hugh,

would you please merge the following two commits into
https://github.com/papyri/idp.data/tree/master/HGV_meta_EpiDoc

they are:
papyri/idp.data@c160cff
and
papyri/idp.data@524d77c

found at:
https://github.com/papyri/idp.data/commits/xwalk

These provide "metadata" for SB XXVIII; P.Coles; P.Tebt.Pad. I. Since SB already exista as series, a new volume should appear in:
http://papyri.info/browse/hgv/SB

Neither P.Coles nor P.Tebt.Pad. I exist so would you please do the necessary so that they are included in:
http://papyri.info/browse/hgv/

At
https://github.com/papyri/idp.data/blob/master/RDF/collection.rdf#L1328-L1333
I added the relevant information in
https://github.com/papyri/idp.data/tree/master/RDF

Display problem: disappearing initial letter

The XML of the following line is correct:
https://github.com/papyri/idp.data/blob/master/DDB_EpiDoc_XML/p.oxy/p.oxy.47/p.oxy.47.3338.xml#L79
in particular
<expan>αἶγ<ex>ας</ex></expan>
is correctly encoded. It is preceded by whitespace and before that
<num value="110">ρ<supplied reason="lost">ι</supplied></num>

When this is displayed in preview in the editor and in the navigator what we see in line 7 is:
ρ[ι] ἶγ(ας)
http://papyri.info/ddbdp/p.oxy;47;3338

In other words the initial alpha is missing.

I assume this must be related to an XSLT problem. It should be fixed. There have been some submissions to the board with attempts to correct this. It is usually the case that the underlying XML is correct.

Filter behaviour

First of all the new reloading does seem to have solved the problems mentioned in #36

My question was: show me all files where Homerus is the author and there is a text div with content.

Actions taken.
Navigate via authors
http://dev.papyri.info/authors
http://dev.papyri.info/authors#H
http://dev.papyri.info/dispatch/search?AUTHOR=Homerus
nice 1689 hits
now using (at the bottom)
Has Transciptions and choosing (true 37) [which seems about right]
I arrive at
http://dev.papyri.info/dispatch/search?TRANSC=true&DATE_MODE=LOOSE&DOCS_PER_PAGE=15
which displays ALL texts across DDB and DCLP which have a transcription.

Would be nice to arrive at the 37.

Inconsistency in TM search

http://papyri.info/#
enter 8988
leads to http://papyri.info/ddbdp/bgu;1;224dupl
So fine. For ddbdp/hgv files things work well.

Back to the same search interface http://papyri.info/#
enter 64248
I get no hit but see this
Bildschirmfoto 2019-06-05 um 21 24 16

So I decided to look for that number another way.
http://papyri.info/browse/dclp/
http://papyri.info/search?&COLLECTION=dclp&SERIES=tm
now I enter 64248 into the ID # box
Bildschirmfoto 2019-06-05 um 21 26 35

No hits and I see this
Bildschirmfoto 2019-06-05 um 21 27 16

but I know that this TM number is in the system
http://papyri.info/dclp/64248

So searching for a TM number that is anchored in the DCLP world is not functioning as we would like it to.

TM Number search not working for DCLP files

http://dev.papyri.info/
now call up TM number search
type in 64127 (TM number for a DCLP record) hit enter button.
Leads to
Not Found
The requested URL /dclp/64127 was not found on this server.

Apache/2.2.15 (Scientific Linux) Server at papyri.info Port 80

this pushes us through to
papyri.info/dclp/64127 NOT dev.papyri.info

Does that mean that when this goes live it WILL in fact work? See below.

Accessing search results not working well

Searches involving THEN show a hit. But if you click on the hit it returns an HTTP Status 400 – Bad Request

So
Bildschirmfoto 2019-05-17 um 14 21 55

Then
Bildschirmfoto 2019-05-17 um 14 23 54
Which uses the URL:

http://papyri.info/search?STRING=(υμων+THEN+δεσποτων)~1chars&no_caps=on&no_marks=on&target=text&DATE_MODE=LOOSE&DOCS_PER_PAGE=15

returns
Bildschirmfoto 2019-05-17 um 14 25 15
where the URL is

http://papyri.info/ddbdp/p.grenf;1;60?rows=2&start=0&fl=id,title&fq=untokenized_ia:/@υμων.{1,1}δεσποτων@/&p=0&t=0

Display in browser tabs

I called up papyri.info and have six tabs open: papyri.info entry page, PN search page (hit the Search data button), home user_dashboard, DDB board, HGV board, DCLP board.

This is what they look like:

Bildschirmfoto 2019-05-23 um 17 37 13

Papyri.info | PN Search | DCLP | DCLP | DCLP | DCLP

We do not want DCLP appearing here. I have forgotten what it used to be when one was in the boards before DCLP was part of the system. There might be a nice argument for displaying DCLP for the DCLP board, DDB for the DDB board, HGV for the HGV board, APIS for all the APIS boards, Transl for the Translation board.

For an editor who is working that would be very helpful.

If, however, that is more work, then please replace DCLP with Papyri.info or whatever it used to be.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.