Re: Updates on Stratml- styled files are ready

[Owen Ambur]

Naval, this seems to have gone far more smoothly than I had anticipated.  

I received your .zip file, unpacked it, and uploaded it to my stratml.us/docs folder.

Then I used Notepad to edit my sitemap and posted the revision at https://stratml.us/docs/sitemap.xml 

I ran Joe Carmel's sitemap catalog script and posted the results at https://stratml.us/docs/catalogsitemap.html

I also checked to see that a couple of the files open in my XForms and have not seen any problems with that yet.

If I don't find any issued in the next couple days, I'll just need to know how to pay you $432 [$18 X 24 hours) for that apparently successfully completed project.  However, beyond that, see my comments below in bold and [brackets].

Owen Ambur

https://www.linkedin.com/in/owenambur/

On Friday, December 9, 2022 at 11:32:22 AM EST, Naval Sarda <nsa...@epicomm.net> wrote:

Please see below

-------- Forwarded Message --------

Subject:	Updates on Stratml- styled files are ready
Date:	Fri, 9 Dec 2022 21:40:24 +0530
From:	Sudarshana <sudar...@epicomm.net>
To:	Naval Sarda <nsa...@epicomm.net>
CC:	jitendras <jite...@epicomm.net>, Balasaheb <balas...@epicomm.net>, kom...@epicomm.net

Owen,

We have downloaded recent original xml files and made it compatible for indexing. Also we have added style tag in each of those files. Attached zip file contains all updated files, along with the stylesheet file which we are using in all files.

To make files compatible for indexing we had to remove (xmlns,xmlns:xsi,xsi:schemaLocation,Type,xmlns:stratml,xmlns:my,xmlns:xd) these attributes and "stratml:" keyword from the tags. We had to replace some special characters like &, ",' etc. We can provide another set of files in case you don't want these tags to be removed for your other use.

[Hopefully, none of the files containing special characters were created or edited with my XForms, because they are supposed to be creating valid XML documents and I have never found them not to be doing so.  If they are doing that, I'll need to find out why and where and get the problem(s) fixed.]

[However, I need to learn more about the other changes that needed to be made in order to import the files into BaseX.  While I don't know exactly why those all of those attributes are included, I trust there are reasons to do so and I don't want the authoritative sources of the files to exclude them without understanding the full implications.  Moreover, I don't believe they should be removed on the stratml.us site or anywhere else on the Web that the original sources of StratML files may reside.  Instead, they should be removed upon importation and indexing in the query service.  Recall that the query service is an index of metadata and not a content repository responsible for presentation of the files themselves, only discrete elements from them in the query results listings.]

We have kept only one version of files for original xml and its styled xml. So no need to maintain separate files. Currently we have uploaded these files in our application but application is not yet ready for you to review as we are resolving few of the issues.

[As per our previous exchange, eventually it is my intent to stop maintaining plain XML renditions of the files on the stratml.us site in favor of just providing the styled versions plus PDF for those that are among the most valuable among them.  However, I may continue posting the plain XML as well for a while, until I'm comfortable they are no longer needed.  One of the purposes for which I prefer having them, for example, is that when I create new plans/reports for organizations already included in the collection, it is easier to copy their <Identifier>s out of the plain XML than the source of the styled renditions.  Eventually, autoring/editing services will facilitate appropriate reuse of the identifiers, including in the stratml:Relationship elements, but for now copying and pasting the org's identifiers from the plain XML is not particularly cumbersome.  For goals and objectives, it is easy to copy their identifies from their URLs when they are displayed in the browser.]

Regarding import functionality of the xml files , we have 2 options.

1. We can provide UI on web application to pick the single single files or zip file for bulk upload. To avail this functionality user need to log in into application then only he can see the button for this functionality. In  the back-end we will make required manipulation in the files and put the files in respective folders.

2. Another option is, we will provide you one folder location, where you can upload your files. We will run one script on regular interval which will import those files in the application.

[The first option seems preferrable, particularly for ad hoc importing of single files at a time.  However, I don't think I'd want to have to deal with .zip files very often.  Now that we've done that for the entire collection, I shouldn't have to do it again anytime soon.  On the other hand, with reference to the second option, it would be nice to be able to FTP groups of files for indexing and execute the database import function semi-automatically.  So depending upon the additional cost, I may wish to have both option at some point in the future, keeping in mind that we will also want to enable other, unauthenticated users to submit files for indexing in a future release of the service.] 

Please tell us your choice so that we can provide you required estimations for that functionality. This functionality was not added in the initial estimations. You can refer earlier mail which had original estimations or we can share the initial estimates sheet on Monday.

[Recall that I consider basic import capability by me to be an inherent feature of the initial release and I don't view the initial project as complete until I have such capability.  However, I am open to renegotiating the cost if it is not excessive.  In the meantime, I will be most interest to see if presentation of the search results have been corrected now that the identifiers for the goals and objectives can be properly referenced and point directly to them in the docs folder on the stratml.us site.  I'm not sure that you or your developer have grasped that concept yet.]

[Finally, again, I am pleasantly surprised the steps outlined in my reply above seem to have gone so smoothly.  I won't be surprised if as yet unseen problems crop up.  However, I am optimistic that we can work through them provided we avoid making assumptions and clearly communicate our thoughts and expectations.] 

-- 

Thanks & Regards
Sudarshana