<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
<br>
first of all - <br>
<br>
<div class="moz-cite-prefix">On 31.01.2017 12:14,
<a class="moz-txt-link-abbreviated" href="mailto:bexis2-dev@listserv.uni-jena.de">bexis2-dev@listserv.uni-jena.de</a> wrote:<br>
</div>
<blockquote
cite="mid:mailman.45083.1485861281.26150.bexis2-dev@listserv.uni-jena.de"
type="cite">
<pre wrap="">Hello Roman,
I am not a specialist in dealing with XML schema definitions.
So I have a few questions referring to these definitions.
1. In the schemas you sent I find the following header in schemaPDwithoutDS.xsd:
</pre>
<blockquote type="cite">
<pre wrap=""><xsd:schema xmlns:xsd=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema">"http://www.w3.org/2001/XMLSchema"</a>
targetNamespace=<a class="moz-txt-link-rfc2396E" href="http://www.bgc-jena.mpg.de">"http://www.bgc-jena.mpg.de"</a>
xmlns:bgc=<a class="moz-txt-link-rfc2396E" href="http://www.bgc-jena.mpg.de">"http://www.bgc-jena.mpg.de"</a>
xmlns:xsi=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.bgc-jena.mpg.de">"http://www.bgc-jena.mpg.de"</a> elementFormDefault="qualified<a class="moz-txt-link-rfc2396E" href="xml:lang=">"
xml:lang="</a>en">
</pre>
</blockquote>
<pre wrap="">
My understanding ist that the namespace bgc is referred to threefold:
– the target of this XML schema definition is <a class="moz-txt-link-rfc2396E" href="http://www.bgc-jena.mpg.de">"http://www.bgc-jena.mpg.de"</a>
– the default namespace in this XML schema is <a class="moz-txt-link-rfc2396E" href="http://www.bgc-jena.mpg.de">"http://www.bgc-jena.mpg.de"</a>
– in addition the prefix "bgc" is assigned to the namespace <a class="moz-txt-link-rfc2396E" href="http://www.bgc-jena.mpg.de">"http://www.bgc-jena.mpg.de"</a>
The last one seems to be superfluous, to me it seems that you need either a specific ("bgc") or a default definition for a given namespace. Or am I mistaken?</pre>
</blockquote>
The schema was generated a while ago (around 2007). We all were not
part of the former team. There was never a complete review of the
schema. We probably review it (during the next 6 month).<br>
<br>
<blockquote
cite="mid:mailman.45083.1485861281.26150.bexis2-dev@listserv.uni-jena.de"
type="cite">
<pre wrap="">
The namespace bgc is used in either ref (always "bgc:source")
</pre>
<blockquote type="cite">
<pre wrap=""><xsd:attribute ref="bgc:source"/>
</pre>
</blockquote>
<pre wrap="">
or several xpath attributes:
</pre>
<blockquote type="cite">
<pre wrap=""><xsd:selector xpath="bgc:owner"/>
<xsd:selector xpath="bgc:keyword"/>
…
</pre>
</blockquote>
<pre wrap="">
While I can understand the latter usage to enforce uniqueness on the respective entries (though not the necessity of the "bgc:"), I don't understand the effect of the former ref attribute. Can you explain?</pre>
</blockquote>
<br>
The ref refers to an attribut called "bgc:source". You will find it
in the baseTypes.xsd schema. That means on that position an
attribute exists.<br>
<br>
<blockquote
cite="mid:mailman.45083.1485861281.26150.bexis2-dev@listserv.uni-jena.de"
type="cite">
<pre wrap="">
2. The other question is that when importing the schema into the BExIS 2.10 system, I am asked for fields giving the title and a description of the data. I didn't find any description in the metadata schema. Is this intentional?</pre>
</blockquote>
Not intentional but also not intuitional (intuitive) enough.
The mapping asks you to link to a field in your metadata structure
where a description (field) is. In the BE(xIS) metadata usually the
bgc:methodology/bgc:introduction node is used for it. Maybe not the
best place and having something called description or abstract in
metadata would fit better. But that is how this metadata structure
look at the moment...<br>
<br>
<br>
<blockquote
cite="mid:mailman.45083.1485861281.26150.bexis2-dev@listserv.uni-jena.de"
type="cite">
<pre wrap="">
All the best
Thomas
</pre>
<blockquote type="cite">
<pre wrap="">Am 20.01.2017 um 16:25 schrieb <a class="moz-txt-link-abbreviated" href="mailto:bexis2-dev@listserv.uni-jena.de">bexis2-dev@listserv.uni-jena.de</a>:
Hi Thomas,
regarding the metadata schema, please find attached a ZIP file with the
latest schema of the Exploratories.
The main XSD file is: schemaPDwithoutDS.xsd
The other 2 files are dependencies.
All 3 files need to be uploaded to the system first (Collect > Push Big
File). Then in Manage Metadata Structure (in settings/gear symbol) you
should be able to import the main XSD file (select from previously
uploaded).
There is still one small issue with this schema. All fields are
indicated as required fields. This is just because we use a different
way of defining required fields in the XSD. Not a big deal, just needs
someone to go through and change the definition. But haven't got around
to do that. So please ignore the red asterisks in the form, once the XSD
has been imported.
Permissions on system features are managed through the admin menue
(settings): Feature Permissions
Then click on the Metadata Management (the term, not the checkbox) and
you will see all users and their permission on this feature. Note: any
change there takes effect immediately, without further confirmation.
Regarding your other error message, Sven will reply to you.
Best regards,
Roman
Am 20.01.2017 um 12:07 schrieb <a class="moz-txt-link-abbreviated" href="mailto:bexis2-dev@listserv.uni-jena.de">bexis2-dev@listserv.uni-jena.de</a>:
</pre>
<blockquote type="cite">
<pre wrap="">Hello Roman,
thanks for the swift reply.
We are looking forward to the "Party Package" and would love to take you up on the offer of a "2 day session in Göttingen and do the migration jointly."
It sounds like a good idea to wait with serious efforts to transfer the data until the next release, but I would like to tinker with the metadata definition, import, export etc., thus any helpful files would be very welcome.
I still have to work on my local installation, though, right now I get on
<a class="moz-txt-link-freetext" href="http://bexis2.10/SAM/Account/MyAccount">http://bexis2.10/SAM/Account/MyAccount</a>
an error message
42703: Spalte securityqu0_.title existiert nicht
Description: An unhandled exception occurred during the execution of the current web request.
Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Npgsql.NpgsqlException: 42703: Spalte securityqu0_.title existiert nicht
Which permissions do I need for the Metadata Schema Management, and where and how are they granted?
Cheers
Thomas
</pre>
<blockquote type="cite">
<pre wrap="">Am 19.01.2017 um 18:48 schrieb <a class="moz-txt-link-abbreviated" href="mailto:bexis2-dev@listserv.uni-jena.de">bexis2-dev@listserv.uni-jena.de</a>:
Hello Thomas,
I now recall I promised to provide you with the adapted XSD of the
Exploratories Project a few month ago. Sorry, I didn't follow up on
that. I just don't have it right now, but will get back to you on this
by tomorrow.
With this XSD you will have very similar elements of the metadata as you
are used to in BEXIS 1. And if you like to change something or add
another schema to the system, thats easily possible. As you know, BEXIS
2 can work with multiple schemas at the same time.
However, it will not be exactly the same schema, since a number of
things have changed in BEXIS 2, e.g. Data Structures are managed
separately from the metadata in BEXIS 2. Also, we are currently working
on the linkage between the metadata and the so called "Party Package"
(managing projects, people, organisations, etc). This will be available
in the next release in May 2017. BTW, this will be a dedicated release
to support the migration from B1 to B2.
For the transfer of all entities at database level (data, metadata,
users, permissions, etc.) most of the scripts are ready by now. I'm not
sure how self-explanatory they are. Perhaps we have to set up a 2 day
session in Göttingen and do the migration jointly. I suspect this will
need some more preparation and testing before-hand. What's your timeline
on that?
Regarding the Metadata Schema Management, are you sure the required
feature permissions are set for you? We are not aware of any problem
there. It works for all our instances.
best wishes
Roman
Am 18.01.2017 um 16:11 schrieb <a class="moz-txt-link-abbreviated" href="mailto:bexis2-dev@listserv.uni-jena.de">bexis2-dev@listserv.uni-jena.de</a>:
</pre>
<blockquote type="cite">
<pre wrap="">Hello folks,
I might have asked this before, but am not aware of any satisfying answer: are there any predefined metadata and data structures available with BExIS 2, in particular to ease the transfer from BExIS 1 to BExIS 2?
We have about 200 structured and about 600 unstructured datasets in our current BExIS 1 database and want to move to BExIS 2 in the (near) future.
In principle it should be easy to transfer at least the unstructured datasets to BExIS 2, but I don't see the metadata structure required. This should be constructed somehow from the schema definitions used in BExIS 1:
schema.xsd which calls
baseTypes.xsd
researchObjects.xsd
dataStructure.xsd
but I am not quite sure how to do this.
Has somebody done this and can provide a suitable schema definition?
And what are the experiences concerning structured datasets?
An additional problem is that I am not able to manage Metadata structures, my BExIS 2.10 tells me
Access denied!
Reason: You are not authorized.
Any help would be highly appreciated…
With best regards
Thomas Fischer
--
Thomas Fischer PhD
Research and Development
SFB 990 EFForTS | INF-Project
Georg-August-Universität Göttingen
Niedersächsische Staats- und Universitätsbibliothek Göttingen
D-37070 Göttingen
Papendiek 14 (Historical Building, Room 2.407)
+49 551 39-33883 (Tel.)
+43 662 621498 (Tel.)
+49 551 39-33856 (Fax)
<a class="moz-txt-link-abbreviated" href="mailto:fischer@sub.uni-goettingen.de">fischer@sub.uni-goettingen.de</a>
<a class="moz-txt-link-freetext" href="http://www.sub.uni-goettingen.de/">http://www.sub.uni-goettingen.de/</a>
<a class="moz-txt-link-freetext" href="http://rdd.sub.uni-goettingen.de/">http://rdd.sub.uni-goettingen.de/</a>
<a class="moz-txt-link-freetext" href="http://vifamath.de/">http://vifamath.de/</a>
_______________________________________________
bexis2-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bexis2-dev@listserv.uni-jena.de">bexis2-dev@listserv.uni-jena.de</a>
<a class="moz-txt-link-freetext" href="https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev">https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev</a>
</pre>
</blockquote>
<pre wrap="">
--
Roman Gerlach
Kontaktstelle Forschungsdatenmanagement
BExIS++ Projektkoordinator
Friedrich-Schiller-Universität Jena
Leutragraben 1, Jentower 17N04
07743 Jena
Tel.: +49-(0)3641-948968
Email: <a class="moz-txt-link-abbreviated" href="mailto:roman.gerlach@uni-jena.de">roman.gerlach@uni-jena.de</a>
Web: <a class="moz-txt-link-freetext" href="http://www.uni-jena.de/forschungsdatenmanagement.html">http://www.uni-jena.de/forschungsdatenmanagement.html</a>
<a class="moz-txt-link-freetext" href="http://bexis2.uni-jena.de/">http://bexis2.uni-jena.de/</a>
_______________________________________________
bexis2-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bexis2-dev@listserv.uni-jena.de">bexis2-dev@listserv.uni-jena.de</a>
<a class="moz-txt-link-freetext" href="https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev">https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
bexis2-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bexis2-dev@listserv.uni-jena.de">bexis2-dev@listserv.uni-jena.de</a>
<a class="moz-txt-link-freetext" href="https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev">https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev</a>
</pre>
</blockquote>
<pre wrap="">
--
Roman Gerlach
Kontaktstelle Forschungsdatenmanagement
BExIS++ Projektkoordinator
Friedrich-Schiller-Universität Jena
Leutragraben 1, Jentower 17N04
07743 Jena
Tel.: +49-(0)3641-948968
Email: <a class="moz-txt-link-abbreviated" href="mailto:roman.gerlach@uni-jena.de">roman.gerlach@uni-jena.de</a>
Web: <a class="moz-txt-link-freetext" href="http://www.uni-jena.de/forschungsdatenmanagement.html">http://www.uni-jena.de/forschungsdatenmanagement.html</a>
<a class="moz-txt-link-freetext" href="http://bexis2.uni-jena.de/">http://bexis2.uni-jena.de/</a>
_______________________________________________
bexis2-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bexis2-dev@listserv.uni-jena.de">bexis2-dev@listserv.uni-jena.de</a>
<a class="moz-txt-link-freetext" href="https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev">https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
bexis2-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bexis2-dev@listserv.uni-jena.de">bexis2-dev@listserv.uni-jena.de</a>
<a class="moz-txt-link-freetext" href="https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev">https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Andreas Ostrowski
Datenmanagement Biodiversitaets-Exploratorien
Friedrich-Schiller-Universität Jena
Institut für Informatik
Leutragraben 1, Jentower
07743 Jena
Tel.: ++ 49 3641 9 46431
E-Mail: <a class="moz-txt-link-abbreviated" href="mailto:andreas.ostrowski@uni-jena.de">andreas.ostrowski@uni-jena.de</a>
WWW: <a class="moz-txt-link-freetext" href="http://www.biodiversity-exploratories.de">http://www.biodiversity-exploratories.de</a>
--</pre>
</body>
</html>