information hidden in attributes

[holfordm]

@Archpoet pointed out today that some fields in the Armenian catalogue contain only attributes, and that this information doesn't display. The example given was this handNote

armenian-mss/collections/MS_Arm_d_1.xml

Line 65 in de252c5

<handNote scope="major" script="Bolorgir"/>

In this case the best solution might be for @andrew-morrison to write an XSLT script to extract the @script value and display it additionally inside the element. <handNote scope="major" script="Bolorgir">Bolorgir</handNote>.

Are there other cases in this catalogue of elements with meaningful attributes but no text content?

[andrew-morrison]

Dimensions too, but they're missing any actual figures.

I can write a script in the New Year to insert content. It can be just the same word as in the attribute, or more than that. For example, here's one of Mohammad Emami's in the Wadham collection, in the Fihrist catalogue:

https://github.com/fihristorg/fihrist-mss/blob/bf002356552d31793afe3d545a6e9369fc9393b5/collections/wadham%20college%20(university%20of%20oxford)/WadhMinasian_210.xml#L110

@Archpoet: Just tell me what text you want for each of the following:

• Bolorgir
• Erkatagir
• Notrgir
• Print
• unknown

[Archpoet]

Andrew, I will provide you with a brief description of each type of script within a couple of days, something like the example you shared with me. The main issue that we have discussed with @holfordm is however that I will need some general training in working with xml files and that we need a basic template for new entries.

[andrew-morrison]

I have run a script on the Armenian records. If you look a any manuscript pages now (e.g. MS. Arm. d. 5) you'll see under Hand(s) the script is now displayed (or "Unknown" in the five records which lack the information.)

That is because each TEI now contains something like the following:

<handDesc>
   <handNote scope="major" script="erkatagir">Written in <ref target="https://armenian.bodleian.ox.ac.uk/about#erkatagir">Erkat‘agir</ref> script</handNote>
</handDesc>

The ref element points to the about page on the web site, which is where I have put the long descriptions of each type of script that you send me. If there is anything about that page you want to change or add, let me know.

Does this look reasonable?

BTW, @holfordm is working on a template.

[Archpoet]

Thank you, Andrew. It works absolute fine and I think it is sufficient. The only thing that I am worried about is the files we have been working on (not many but still some). Should we download the files anew and start the work from scratch for those files, or will you be able to collate the two?

[andrew-morrison]

If you open GitHub Desktop, and select Pull from the Repository menu, it should download all my changes and merge them into your local copies of the files. If you have made minor edits in other parts of the records, not in or near the handNote element, it should be able to do so automatically. Otherwise, it will display a message about "conflicts", and you'll need to edit the affected records, because it will have put both versions of the handNote one after the one, and you'll need to pick one and delete the other (and extra lines it will have added to mark the two.) Then commit and select Push from the Repository menu to make your changes available to me (and let me know if you want them published to the web site.)

[Archpoet]

I did. This is the message I receive:

"error: Your local changes to the following files would be overwritten by merge:
collections/MS_Arm_b_1.xml
Please commit your changes or stash them before you merge.
Aborting"

[andrew-morrison]

OK, that means you have changes, which do clash with mine, but haven't committed them yet. If you want to keep your changes, click the Commit to master button in the bottom-right. Then try Pull again (then it will probably display the message about conflicts. If you don't want to keep your changes, right-click on the files listed under Changes and select Discard Changes... Then try Pull again.

[Archpoet]

I have almost finished the one of the MS Arm b.1. Shall I complete it and then commit it, or is it fine to do it now?

[andrew-morrison]

You can commit now, merge in my change to handNote, then continue working on it some more (including adding more detail to the handNote, if you wish.)

In general, it is better to commit as often as possible. Committing only records the changes you've made in your local copy (creating a version you can revert back to if you change your mind about subsequent changes). Nobody else can see you your commits until you push. Pushing is what updates the records on the GitHub servers, making your changes available for everyone else, and allowing me to publish those changes to the web site (it is also good to push frequently, as that avoids conflicts, but not if that would mean making available something which you wouldn't want to see on the web site.)

I hope that makes sense.

[Archpoet]

It makes sense. The problem is my "Commit to Master" button cannot be clicked; it's not highlighted. I am working on MAC: is there anything I should do first?

[andrew-morrison]

I have GitHub Desktop on a Mac. Obviously, I cannot replicate the state of your local copy or know if you are using the same version of the software as me. But one or both of the following should enable to the commit button:

• Is there at least one checkbox selected in the list of changed files?
• Is there some text in the summary box below the list of files, but above the commit button? It should pre-fill that with something (e.g. "Update MS_Arm_b_1.xml") but you can change it. (As mentioned above, committing creates points to which you can revert back in the future, so make it something that will remind you what you did. Think the subject line of an email. The larger description field is optional, and can contain more details.)

[Archpoet]

I realised I had to write a "Summary" to be able to Commit it. So, I pressed the Commit to master and now it's gone.