From bexis2-dev at listserv.uni-jena.de Mon Jan 30 11:56:15 2017 From: bexis2-dev at listserv.uni-jena.de (bexis2-dev at listserv.uni-jena.de) Date: Mon, 30 Jan 2017 10:56:15 +0000 Subject: [BEXIS2-Dev] Default Data Structure In-Reply-To: References:

Message-ID: Hello Roman, there is nothing in the older database that I want to keep, but eventually there must be a way to move from one version to the other without discarding the current database. Unfortunately, I had a hard time in creating a new working database. I tried to follow the description in "BEXIS2100_Installation_Manual.pdf": > 4.1.4.1. Create empty database on PostgreSQL > > Open pgAdmin. Double click on the “PostgreSQL 9.3 (localhost: 5432)”. A popup window will open where you need to enter the password for user ‘postgres’. Please enter “1” as the password you defined when you installed PostgreSQL. I have pgAdmin III, and "Double click on the 'PostgreSQL 9.3 (localhost: 5432)'" has no effect. In particular, I cannot enter or change a password. > Then in the Object browser section, Right click on “Databases” node and create a new database. Enter “BEXIS” as a database name. I dropped the existing "BEXIS" database and created a new one. The owner was automatically set to postgres. pgAdmin gives me the picture below: But trying to access bexis2.10 gives the result: http://bexis2.10/SAM/Account/LogOn?ReturnUrl=%2f Serverfehler 401 - Nicht autorisiert: Zugriff aufgrund ungültiger Anmeldeinformationen verweigert. Die angegebenen Anmeldeinformationen berechtigen Sie nicht, dieses Verzeichnis oder diese Seite anzuzeigen. Since they are connected to the same database, I get the same message from bexis2.9. Now I changed Web.config. (It was on "false". What is the comment there in Web.config supposed to mean? Does Bexis come with a predefined database?) Now I actually get access, can register again. But I don't have administrative access. I get Access denied! Reason: You are not authorized. for every entry in the admin menu. Do you have any idea how to fix this? All the best Thomas > Am 26.01.2017 um 17:25 schrieb bexis2-dev at listserv.uni-jena.de: > > Hi Thomas, > > I guess something went wrong with the previous upgrade to BEXIS 2.10. > Your database seems to be on an older version. Do you have any data in > the database that you want to keep? If not I'd suggest to redo the > installation with a clean database. > > There is currently no automatic migration of the database between > different versions. Unfortunately, there are always a few changes in the > database schema. So simply overwriting the application wont work. > > If you need any help with the installation, please let us now. > > Best regards, > Roman > > > Am 25.01.2017 um 16:20 schrieb bexis2-dev at listserv.uni-jena.de: >> Hello Roman, >> >> the bar on the dashboard says "BEXIS 2.10 - Home ". This was extracted from a file "BPP2100_full.zip" from 6. Dezember 2016 02:27, and the "BPPR210_Website" inside is from 3. Dezember 2016 07:48. >> Is there anything newer and better? >> >> All he best >> Thomas >> >>> Am 24.01.2017 um 16:56 schrieb bexis2-dev at listserv.uni-jena.de: >>> >>> Hello Thomas, >>> >>> which BEXIS version are you using? From the list of features permissions >>> it seems that this is not BEXIS 2.10.0. Metadata Management was >>> different/not available in earlier versions. >>> >>> best regards >>> Roman >>> >>> >>> >>> Am 24.01.2017 um 10:53 schrieb bexis2-dev at listserv.uni-jena.de: >>>> Hello, >>>> >>>> thanks for the metadata scheme(s). But I'm still stuck with the management question. >>>> >>>> The "Manage Data Permissions" gives an error: >>>> >>>> Server Error in '/' Application. >>>> Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. >>>> >>>> "Manage Feature Permissions" yields the following list: >>>> >>>> • BExIS >>>> • Administration >>>> • Users Management >>>> • Groups Management >>>> • Data Management >>>> • Feature Management >>>> • Search >>>> • Dataset Maintenance >>>> • Data Collection >>>> • Search >>>> • Data Collection >>>> • Dataset Creation >>>> • Dataset Submission >>>> • Research Plan >>>> • Data Attribute Manager >>>> • Unit Manager >>>> • Data Dissemination >>>> >>>> without "Metadata Management". I granted all available rights, but still get the >>>> "Access denied!" >>>> when I select "Manage Metadata Structure". >>>> Help! >>>> >>>> Cheers >>>> Thomas >>>> >>>> >>>>> Am 20.01.2017 um 16:25 schrieb bexis2-dev at listserv.uni-jena.de: >>>>> >>>>> >>>>> 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. >>>>> >>>> >>>> >>>> • BExIS >>>> • Administration >>>> • Users Management >>>> • Groups Management >>>> • Data Management >>>> • Feature Management >>>> • Search >>>> • Dataset Maintenance >>>> • Data Collection >>>> • Search >>>> • Data Collection >>>> • Dataset Creation >>>> • Dataset Submission >>>> • Research Plan >>>> • Data Attribute Manager >>>> • Unit Manager >>>> • Data Dissemination >>>> >>>> >>>> >>>> _______________________________________________ >>>> bexis2-dev mailing list >>>> bexis2-dev at listserv.uni-jena.de >>>> https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev >>>> >>> >>> -- >>> >>> Roman Gerlach >>> Kontaktstelle Forschungsdatenmanagement >>> BExIS++ Projektkoordinator >>> Friedrich-Schiller-Universität Jena >>> Leutragraben 1, Jentower 17N04 >>> 07743 Jena >>> >>> Tel.: +49-(0)3641-948968 >>> Email: roman.gerlach at uni-jena.de >>> Web: http://www.uni-jena.de/forschungsdatenmanagement.html >>> http://bexis2.uni-jena.de/ >>> >>> _______________________________________________ >>> bexis2-dev mailing list >>> bexis2-dev at listserv.uni-jena.de >>> https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev >> >> >> >> _______________________________________________ >> bexis2-dev mailing list >> bexis2-dev at listserv.uni-jena.de >> https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev >> > > -- > > Roman Gerlach > Kontaktstelle Forschungsdatenmanagement > BExIS++ Projektkoordinator > Friedrich-Schiller-Universität Jena > Leutragraben 1, Jentower 17N04 > 07743 Jena > > Tel.: +49-(0)3641-948968 > Email: roman.gerlach at uni-jena.de > Web: http://www.uni-jena.de/forschungsdatenmanagement.html > http://bexis2.uni-jena.de/ > > _______________________________________________ > bexis2-dev mailing list > bexis2-dev at listserv.uni-jena.de > https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev -------------- nächster Teil -------------- Ein Dateianhang mit HTML-Daten wurde abgetrennt... URL: -------------- nächster Teil -------------- Ein Dateianhang mit Binärdaten wurde abgetrennt... Dateiname : pgadmin.gif Dateityp : image/gif Dateigröße : 32843 bytes Beschreibung: nicht verfügbar URL : -------------- nächster Teil -------------- Ein Dateianhang mit Binärdaten wurde abgetrennt... Dateiname : signature.asc Dateityp : application/pgp-signature Dateigröße : 842 bytes Beschreibung: Message signed with OpenPGP using GPGMail URL : From bexis2-dev at listserv.uni-jena.de Mon Jan 30 13:15:37 2017 From: bexis2-dev at listserv.uni-jena.de (bexis2-dev at listserv.uni-jena.de) Date: Mon, 30 Jan 2017 12:15:37 +0000 Subject: [BEXIS2-Dev] Trash last email In-Reply-To: References:

Message-ID: Hello Roman, I retrieved the Admin password, no need to do anything now. I'll come back to you if I run into new problems . Cheers Thomas -------------- nächster Teil -------------- Ein Dateianhang mit Binärdaten wurde abgetrennt... Dateiname : signature.asc Dateityp : application/pgp-signature Dateigröße : 842 bytes Beschreibung: Message signed with OpenPGP using GPGMail URL : From bexis2-dev at listserv.uni-jena.de Tue Jan 31 12:14:37 2017 From: bexis2-dev at listserv.uni-jena.de (bexis2-dev at listserv.uni-jena.de) Date: Tue, 31 Jan 2017 11:14:37 +0000 Subject: [BEXIS2-Dev] Default Data Structure In-Reply-To: References:

Message-ID: 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: > targetNamespace="http://www.bgc-jena.mpg.de" > xmlns:bgc="http://www.bgc-jena.mpg.de" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns="http://www.bgc-jena.mpg.de" elementFormDefault="qualified" > xml:lang="en"> My understanding ist that the namespace bgc is referred to threefold: – the target of this XML schema definition is "http://www.bgc-jena.mpg.de" – the default namespace in this XML schema is "http://www.bgc-jena.mpg.de" – in addition the prefix "bgc" is assigned to the namespace "http://www.bgc-jena.mpg.de" 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? The namespace bgc is used in either ref (always "bgc:source") > or several xpath attributes: > > > … 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? 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? All the best Thomas > Am 20.01.2017 um 16:25 schrieb bexis2-dev at listserv.uni-jena.de: > > 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 bexis2-dev at listserv.uni-jena.de: >> 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 >> http://bexis2.10/SAM/Account/MyAccount >> 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 >> >>> Am 19.01.2017 um 18:48 schrieb bexis2-dev at listserv.uni-jena.de: >>> >>> 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 bexis2-dev at listserv.uni-jena.de: >>>> 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) >>>> >>>> fischer at sub.uni-goettingen.de >>>> http://www.sub.uni-goettingen.de/ >>>> http://rdd.sub.uni-goettingen.de/ >>>> http://vifamath.de/ >>>> >>>> >>>> >>>> _______________________________________________ >>>> bexis2-dev mailing list >>>> bexis2-dev at listserv.uni-jena.de >>>> https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev >>>> >>> >>> -- >>> >>> Roman Gerlach >>> Kontaktstelle Forschungsdatenmanagement >>> BExIS++ Projektkoordinator >>> Friedrich-Schiller-Universität Jena >>> Leutragraben 1, Jentower 17N04 >>> 07743 Jena >>> >>> Tel.: +49-(0)3641-948968 >>> Email: roman.gerlach at uni-jena.de >>> Web: http://www.uni-jena.de/forschungsdatenmanagement.html >>> http://bexis2.uni-jena.de/ >>> >>> _______________________________________________ >>> bexis2-dev mailing list >>> bexis2-dev at listserv.uni-jena.de >>> https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev >> >> >> >> _______________________________________________ >> bexis2-dev mailing list >> bexis2-dev at listserv.uni-jena.de >> https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev >> > > -- > > Roman Gerlach > Kontaktstelle Forschungsdatenmanagement > BExIS++ Projektkoordinator > Friedrich-Schiller-Universität Jena > Leutragraben 1, Jentower 17N04 > 07743 Jena > > Tel.: +49-(0)3641-948968 > Email: roman.gerlach at uni-jena.de > Web: http://www.uni-jena.de/forschungsdatenmanagement.html > http://bexis2.uni-jena.de/ > > _______________________________________________ > bexis2-dev mailing list > bexis2-dev at listserv.uni-jena.de > https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev -------------- nächster Teil -------------- Ein Dateianhang mit Binärdaten wurde abgetrennt... Dateiname : signature.asc Dateityp : application/pgp-signature Dateigröße : 842 bytes Beschreibung: Message signed with OpenPGP using GPGMail URL : From bexis2-dev at listserv.uni-jena.de Tue Jan 31 14:30:21 2017 From: bexis2-dev at listserv.uni-jena.de (bexis2-dev at listserv.uni-jena.de) Date: Tue, 31 Jan 2017 14:30:21 +0100 Subject: [BEXIS2-Dev] Tenant Documentation Message-ID: Hi all, Attached find the Tenants documentation. Cheers, Nafiseh -- Nafiseh Navabpour BExIS++ Project Research assistant Friedrich-Schiller-University Jena Leutragraben 1, Jentower, 07743 Jena Phone: +49-(0)3641-946443 -------------- nächster Teil -------------- Ein Dateianhang mit HTML-Daten wurde abgetrennt... URL: -------------- nächster Teil -------------- Ein Dateianhang mit Binärdaten wurde abgetrennt... Dateiname : Tenant Documentation.docx Dateityp : application/vnd.openxmlformats-officedocument.wordprocessingml.document Dateigröße : 16766 bytes Beschreibung: nicht verfügbar URL : From bexis2-dev at listserv.uni-jena.de Tue Jan 31 15:50:27 2017 From: bexis2-dev at listserv.uni-jena.de (bexis2-dev at listserv.uni-jena.de) Date: Tue, 31 Jan 2017 14:50:27 +0000 Subject: [BEXIS2-Dev] Default Data Structure In-Reply-To: References:

Message-ID: Hello Roman, I followed your description and managed successfully to import the metadata schema into my bexis2.10 instance. Since we use a slightly (?) different metadata schema from bexis1, I created a set of schema definition files analogously to your set. I validated the xsd file and tried to import it into bexis2.10. But that failed with the message > • Unable to cast object of type > 'System.Xml.Schema.XmlSchemaElement' to type > 'System.Xml.Schema.XmlSchemaGroup'. > • Can not create metadatastructure. which leaves me somewhat puzzled. What are the additional requirements beyond validity for a metadata schema to be imported into bexis2.10? Cheers, Thomas > Am 20.01.2017 um 16:25 schrieb bexis2-dev at listserv.uni-jena.de: > > 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 > -------------- nächster Teil -------------- Ein Dateianhang mit Binärdaten wurde abgetrennt... Dateiname : signature.asc Dateityp : application/pgp-signature Dateigröße : 842 bytes Beschreibung: Message signed with OpenPGP using GPGMail URL : From bexis2-dev at listserv.uni-jena.de Fri Feb 3 14:16:12 2017 From: bexis2-dev at listserv.uni-jena.de (bexis2-dev at listserv.uni-jena.de) Date: Fri, 3 Feb 2017 14:16:12 +0100 Subject: [BEXIS2-Dev] Default Data Structure In-Reply-To: References:

Message-ID: Hi all, first of all - On 31.01.2017 12:14, bexis2-dev at listserv.uni-jena.de wrote: > 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: > >> > targetNamespace="http://www.bgc-jena.mpg.de" >> xmlns:bgc="http://www.bgc-jena.mpg.de" >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >> xmlns="http://www.bgc-jena.mpg.de" elementFormDefault="qualified" >> xml:lang="en"> > My understanding ist that the namespace bgc is referred to threefold: > – the target of this XML schema definition is "http://www.bgc-jena.mpg.de" > – the default namespace in this XML schema is "http://www.bgc-jena.mpg.de" > – in addition the prefix "bgc" is assigned to the namespace "http://www.bgc-jena.mpg.de" > > 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? 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). > > The namespace bgc is used in either ref (always "bgc:source") > >> > > or several xpath attributes: > >> >> >> … > 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? 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. > > 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? 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... > > All the best > Thomas > >> Am 20.01.2017 um 16:25 schrieb bexis2-dev at listserv.uni-jena.de: >> >> 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 bexis2-dev at listserv.uni-jena.de: >>> 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 >>> http://bexis2.10/SAM/Account/MyAccount >>> 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 >>> >>>> Am 19.01.2017 um 18:48 schrieb bexis2-dev at listserv.uni-jena.de: >>>> >>>> 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 bexis2-dev at listserv.uni-jena.de: >>>>> 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) >>>>> >>>>> fischer at sub.uni-goettingen.de >>>>> http://www.sub.uni-goettingen.de/ >>>>> http://rdd.sub.uni-goettingen.de/ >>>>> http://vifamath.de/ >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> bexis2-dev mailing list >>>>> bexis2-dev at listserv.uni-jena.de >>>>> https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev >>>>> >>>> -- >>>> >>>> Roman Gerlach >>>> Kontaktstelle Forschungsdatenmanagement >>>> BExIS++ Projektkoordinator >>>> Friedrich-Schiller-Universität Jena >>>> Leutragraben 1, Jentower 17N04 >>>> 07743 Jena >>>> >>>> Tel.: +49-(0)3641-948968 >>>> Email: roman.gerlach at uni-jena.de >>>> Web: http://www.uni-jena.de/forschungsdatenmanagement.html >>>> http://bexis2.uni-jena.de/ >>>> >>>> _______________________________________________ >>>> bexis2-dev mailing list >>>> bexis2-dev at listserv.uni-jena.de >>>> https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev >>> >>> >>> _______________________________________________ >>> bexis2-dev mailing list >>> bexis2-dev at listserv.uni-jena.de >>> https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev >>> >> -- >> >> Roman Gerlach >> Kontaktstelle Forschungsdatenmanagement >> BExIS++ Projektkoordinator >> Friedrich-Schiller-Universität Jena >> Leutragraben 1, Jentower 17N04 >> 07743 Jena >> >> Tel.: +49-(0)3641-948968 >> Email: roman.gerlach at uni-jena.de >> Web: http://www.uni-jena.de/forschungsdatenmanagement.html >> http://bexis2.uni-jena.de/ >> >> _______________________________________________ >> bexis2-dev mailing list >> bexis2-dev at listserv.uni-jena.de >> https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev > > > _______________________________________________ > bexis2-dev mailing list > bexis2-dev at listserv.uni-jena.de > https://lserv.uni-jena.de/mailman/listinfo/bexis2-dev -- 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: andreas.ostrowski at uni-jena.de WWW: http://www.biodiversity-exploratories.de -- -------------- nächster Teil -------------- Ein Dateianhang mit HTML-Daten wurde abgetrennt... URL: From bexis2-dev at listserv.uni-jena.de Fri Feb 3 14:21:52 2017 From: bexis2-dev at listserv.uni-jena.de (bexis2-dev at listserv.uni-jena.de) Date: Fri, 3 Feb 2017 13:21:52 +0000 Subject: [BEXIS2-Dev] Update Batch Upload Message-ID: Dear Developers! My today Friday update of the Batch Upload programming. - Today I solved issues #8 : Model.Error is not correctly updated - And today I solved issues #11 : Overflow of file management list That was the current Friday update to the batch upload. 1 parent a716988f master Information from last Friday (I think I have forgot to mail this update): Dear Developers! My today Friday update of the Batch Upload programming. - Today I solved issues #9 : Order file processing list is not correctly updated Is a file is specified for processing multiple times, so this is inserted more than once in the list of the data model. - Today I also solved issues #5 : Click "Next" order file write. Click "Next" to write DataSet and select files in the order file. - Code polished That was the current Friday update to the batch upload. 1 parent 07d13575 master Mit freundlichen Grüßen/With kind regards/Med vänliga hälsningar Thorsten Hindermann ---------------------------------------------------------------------------- ---------------------- Thorsten Hindermann DV-Systemtechniker Arbeitsgruppe "Basisdienste und Organisation" Tel.: +49 551 201-1837, E-Mail: Thorsten.Hindermann at gwdg.de ---------------------------------------------------------------------------- ---------------------- Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen (GWDG) Am Faßberg 11, 37077 Göttingen, URL: http://www.gwdg.de Tel.: +49 551 201-1510, Fax: +49 551 201-2150, E-Mail: gwdg at gwdg.de Service-Hotline: Tel.: +49 551 201-1523, E-Mail: support at gwdg.de Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Norbert Lossau Sitz der Gesellschaft: Göttingen Registergericht: Göttingen, Handelsregister-Nr. B 598 ---------------------------------------------------------------------------- ---------------------- Zertifiziert nach ISO 9001 ---------------------------------------------------------------------------- ---------------------- -------------- nächster Teil -------------- Ein Dateianhang mit HTML-Daten wurde abgetrennt... URL: -------------- nächster Teil -------------- Ein Dateianhang mit Binärdaten wurde abgetrennt... Dateiname : BEXIS-BatchUpload.JPG Dateityp : image/jpeg Dateigröße : 106842 bytes Beschreibung: nicht verfügbar URL : -------------- nächster Teil -------------- Ein Dateianhang mit Binärdaten wurde abgetrennt... Dateiname : smime.p7s Dateityp : application/pkcs7-signature Dateigröße : 6411 bytes Beschreibung: nicht verfügbar URL : From bexis2-dev at listserv.uni-jena.de Fri Feb 3 14:30:24 2017 From: bexis2-dev at listserv.uni-jena.de (bexis2-dev at listserv.uni-jena.de) Date: Fri, 3 Feb 2017 14:30:24 +0100 Subject: [BEXIS2-Dev] BEXIS UserDevConf 2017 - save the date! Message-ID: Dear all, please mark your calendar: the 3rd BEXIS User and Developer Conference will take place on June 15-16, 2017 in Jena (Germany). This 2-day conference will bring together users, developers and data managers of both BExIS & BEXIS 2 data management platforms. It is a community gathering featuring keynote talks, user presentations and workshops. More information coming soon. Best regards, Roman -- Roman Gerlach Kontaktstelle Forschungsdatenmanagement BExIS++ Projektkoordinator Friedrich-Schiller-Universität Jena Leutragraben 1, Jentower 17N04 07743 Jena Tel.: +49-(0)3641-948968 Email: roman.gerlach at uni-jena.de Web: http://www.uni-jena.de/forschungsdatenmanagement.html http://bexis2.uni-jena.de/