[eml-dev] [morpho-dev] Bug in import MS Access to morpho

[Matt Jones]

Jing,

I suggest that for the entityName you just use the name of the table, as
that is what the entity really represents in this case.  The entity is
embedded in a larger physical object (the access db).  For objectName, I
would use the name of thee access file.  That would be accurate, in that
each of the entities described in EML is contained in the same object (the
accessdb).  If you find that having non-unique names in objectName is a
problem, then maybe prepend the table name (e.g., "table1-mydata.adb",
"table2-mydata.adb") -- but I don't think there is a requirement that the
objectName be unique, especially for container formats that can contain
multiple entities.

A fixed string in mediumName such as "disk" is fine.  Its not a very useful
field or section.

Matt

On Mon, Dec 7, 2009 at 2:16 PM, Jing Tao <tao at nceas.ucsb.edu> wrote:

> Hi, devs:
>
> I am working on the bug
> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4537
>
> This bug is about generating invalid eml output when user imports a MS
> Access db to morpho.
>
> I took a look and found there are two problems there:
>
> 1. Generating an empty objectName element - <objectName/>
> 2. Generating an empty offline element - <offline/>
>
> They are not hard to be fixed. But I have to make sure I am going to add
> correct value there.
>
> For objectName, in our morpho practice, we usually put physical file name
> there. In MS Access module, each table in MS Access db will be generated a
> dataTable in eml. And each dataTable will have an objectName. If we put a
> physical file name, i.e. database file name, as objectName, so different
> dataTable will have same objectName. For example, text.adp has two tables
> table-one and table-two. In the EML, it will have two dataTable elemnts
> table-one and table-two. Both of them will have a same objectName -
> test.adp.
>
> I am not sure if this is a good idea since eml specification says:
> The name of the data object. This is possibly distinct from the entity name
> in that one physical object can contain multiple entities, even though that
> is not a recommended practice.
>
> For offline element, I will put some hard code such as "Hard Drive" as
> mediumName since Import MS Access Module doesn't have any user input
> interface there.
>
> Any suggestion and comment will be appreciated.
>
> Jing
>
> Jing Tao
> National Center for Ecological
> Analysis and Synthesis (NCEAS)
> 735 State St. Suite 204
> Santa Barbara, CA 93101
> _______________________________________________
> Morpho-dev mailing list
> Morpho-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/morpho-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20091207/c8faec32/attachment.html>