Difference between revisions of "Talk:PubMan Func Spec Genre specific Submission"

From MPDLMediaWiki
Jump to navigation Jump to search
m
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<accesscontrol>PubMan Piloten,,MPDL,,</accesscontrol>
Actually why not linking this table to Publication Types VES ( http://colab.mpdl.mpg.de/mediawiki/ESciDoc_PublicationTypes_VES )?
 
We are doing double work - and it always has to be specified on two places, whenever there is a change :) --[[User:Natasab|Natasa]] 12:01, 1 April 2010 (UTC)
= Diskussionsseite zur genre spezifischen Eingabemaske =
Bitte schreiben Sie Ihr jeweiliges Feedback unter die Überschrift mit dem jeweiligen Genre und '''signieren Sie Ihren Beitrag'''. Hierzu geben sie am Ende Ihres Beitrags einfach vier Tilden ein: <nowiki>~~~~</nowiki>. Nach dem Speichern der Seite ("Save page") erscheint an der Stelle der vier Tilden dann automatisch Ihr Nutzername sowie ein Datums- und Zeitstempel: --[[User:Tanja|Tanja]] 08:48, 6 August 2008 (UTC)
 
Bitte geben Sie auch an ob Ihr Feedback die Easy oder die Full Submission betrifft.
 
General feedback by Karin:
In our institute we need abstract and keyword-> thus we want this in almost all genre types. The user should be able to add information like dates whenever
possible, so we added date a lot of time within the masks.
The drop down menu for dates should follow the order of the dates in the full submission masked (now the drop-down menu is slightly random).
 
Whenever one can fill in a 'Bibliotheks Signatur' -> this is called call number or shelf number and not signature(!)!
 
 
 
 
'''GUI Feedback general:'''
 
If a genre - specific form is offered, it might not cover all fields/meta data provided by the user (maybe he even does not have a clear understanding of the genre). For some cases we need a clear/simple handling of data which is not included in a genre specific form:
 
*Change genre during create item (User defines the genre, fills the form and changes the genre)
*Change genre via edit item
*Ingestion
*New revision
*Use as template
*Fetch MD
*??
 
One way might be to warn and discard all data, not relevant for the current genre. Making it somehow accessible can get complicated on the GUI. --[[User:Rkiefl|Rupert]] 11:44, 18 August 2008 (UTC)
:Would agree with Rupert. In addition keeping data that are not allowed for a genre will always make problems in: regular validation, validation for YB etc. Would propose to discard metadata not allowed for a genre. In case when item is saved, old version of the item can still be viewed with genre-specific metadata. Each version can be of a different genre in fact (if users were changing it each time). An experience from eDoc is also to be considered in this case. --[[User:Natasab|Natasa]] 16:09, 19 August 2008 (UTC)
 
Different labels could be problematic. Here we have for example various labels for 'Source Volume':
 
* Journal Article: 'Volume'
* Book Chapter:    'Volume of Book'
* Teaching:        'Number of Teachware'
 
There is only one metadata 'Source Volume' - right? These labels must be applied in 'View Item Version' as well. Otherwise the user enters 'Number of Teachware' in 'Create Item' and gets 'Source Volume' in 'View Item Version'.
 
It would be better to put a small table into the context sensitive help or apply a tool tip (TITLE Tag) on mouse over: 'Also used as 'Number of Teachware' or ...'.
:To this i would disagree for edit form, but would agree for search form (if there is a search). --[[User:Natasab|Natasa]] 16:09, 19 August 2008 (UTC)
 
If the decision for a genre is a fundamental decision which leads to various appearance of the content section it would perhaps be better to include that into the menu structure.
--[[User:Rkiefl|Rupert]] 08:24, 11 August 2008 (UTC)
 
:probably makes sense during new submission and genre-specific searches. --[[User:Natasab|Natasa]] 16:09, 19 August 2008 (UTC)
== Feedback zu Journal Article ==
 
label: title of Journal => should be: title of article
::why we should duplicate? if the genre is article it is understandable that the label is the title of the article, shall we have different labels for title/genre combination?--[[User:Natasab|Natasa]] 16:09, 19 August 2008 (UTC)
 
include also in easy submission these fields: subject, start page, and end page
 
include also in full submission: date created, date modified, review type
(comments by Karin)
:: Added fields. --[[User:Nicole|Nicole]] 06:52, 26 August 2008 (UTC)
Rupert: This would be one date field with an option to define the date type (see Easy Submission Book) --[[User:Rkiefl|Rupert]] 08:24, 11 August 2008 (UTC)
 
=== eDoc to PubMan mapping issues ===
* how shall we handle issuecontributorfn and issuecorporatebody and issuetitle? In the PubMan submission mask they are not considered. --[[User:Nicole|Nicole]] 06:52, 26 August 2008 (UTC)
 
== Feedback zum Book ==
easy submission:
include place of publication, subject, abstract
 
full submission:
include total number of pages
 
:: Added to genre specific submission. --[[User:Nicole|Nicole]] 06:35, 26 August 2008 (UTC)
 
source genre/source title: should be default value: series, other types not applicable
 
:: Is dependent on GUI. --[[User:Nicole|Nicole]] 06:35, 26 August 2008 (UTC)
 
(comment by Karin)
 
=== eDoc to PubMan Mapping issues ===
* We should add seriescontributorcorporatebody or seriescontributorfn, otherwise this info, which can be entered via eDoc gets lost. --[[User:Nicole|Nicole]] 06:35, 26 August 2008 (UTC)
* Add table of contents? Exists in eDoc and if we don't add it here the information will get lost. --[[User:Nicole|Nicole]] 06:47, 26 August 2008 (UTC)
 
== Feedback zum Book Chapter ==
easy submission:
 
include also: file, file locator, keyword, abstract, creator(s) of book (the editor of a book is much earlier known and a far more
reliable resource than the title of the book), start page of chapter, end page of chapter. We think the
 
full submission:
add total number of pages
 
:: Added fields. --[[User:Nicole|Nicole]] 06:44, 26 August 2008 (UTC)
 
label source genre/source title: these should be default values
 
:: Dependant on GUI decision. --[[User:Nicole|Nicole]] 06:44, 26 August 2008 (UTC)
 
(comments by Karin)
 
=== eDoc to PubMan mapping issues ===
 
* add seriescontributorfn, otherwise this info, which is given in eDoc will get lost. --[[User:Nicole|Nicole]] 06:44, 26 August 2008 (UTC)
 
== Feedback zum Proceedings (Proceedingsband) ==
easy submission:
add keyword, abstract
 
full submission:
add date created, date modified, total number of pages
 
(''comments by Karin)''
 
:: Added fields. --[[User:Nicole|Nicole]] 10:43, 27 August 2008 (UTC)
 
=== eDoc to PubMan mapping issues ===
* shall we add editiondescription, issues, issuetitle, journaltitle, journalabbreviation, seriescontributorcorbaratebody, seriescontributorfn, table of contents? They can be specified via eDoc and would otherwise get lost.
 
== Feedback zum Proceedings Paper (Conference Paper) ==
easy submission:
add file, file upload, keyword, abstract
 
full submission:
add date created, date modified, invited
 
:: Added fields. --[[User:Nicole|Nicole]] 07:04, 26 August 2008 (UTC)
 
other:
source should be a drop-down menu or as now a list of different sources BUT we also need
something for physical description, since a lot of proceedings appear as CD-Rom, DVD, or
only online. Depending on the physical description subsequent fields should be available.
(''comments by Karin)''
:: For physical description the fiel total number of pages will be used. --[[User:Nicole|Nicole]] 07:04, 26 August 2008 (UTC)
::: It doesn't make sense to use the field total number of pages for different sources. Is it possible to choose the source in the field where someone can upload a file, the content type . --Seesko 07:01, 5 September 2008 (UTC) content type is no physical description --[[User:Karin|Karin]] 11:16, 19 September 2008 (UTC)
we still think that the input for physical description should be more standardized (pull-down menu)- citing rules may depend on physical description.--[[User:Karin|Karin]] 11:16, 19 September 2008 (UTC)
 
 
easy submission:
add Start Page and End Page in book, Start Page and End Page in series, Sequence Number of paper (''comment by Elke, 26.08.08'')
 
=== eDoc to PubMan mapping issues ===
* what to do with issuecontributorfn and issue title? Can be entered via eDoc.
* add source.alternativeTitle, as it can be entered via eDoc as it otherwise gets lost.
* what to do with proceedingscontributorfn, publisher, publisheraddress, seriescontributorcorporatebody, seriescontributorfn, titleofproceedings, titleofseries? Not considered in the genre specific entry mask.
--In the last point I agree with Nicole. We need in Pub Man the title of proceedings and of series. --Seesko 06:33, 5 September 2008 (UTC)
 
== Feedback zum Talk ==
easy submission:
add file, file locator, keyword, abstract
:: Added fields. --[[User:Nicole|Nicole]] 07:10, 26 August 2008 (UTC)
 
=== eDoc to PubMan mapping issues ===
* shall we add "table of contents"? It can be entered via eDoc and would otherwise get lost.
 
== Feedback zum  Conference Report ==
add subject, abstract
(comments by Karin)
:: Added fields. --[[User:Nicole|Nicole]] 07:18, 26 August 2008 (UTC)
 
=== eDoc to PubMan mapping issues ===
* shall we add startdate and enddate of event and table of contents? Can be specified via eDoc and will otherwise get lost.
 
== Feedback zum  Poster ==
 
easy submission:
add: subject, abstract, end date of event,
 
full submission:
add date submitted, date accepted, date publ. online, date publ. in print,
source genre, source title, source volume, source issue, source start page and end page,
sequence number and identifier, end date of event, invited
also add a possibility to enter a physical description
''(comments by Karin)''
 
:: Added fields. For physical description "total number of pages" should be used. --[[User:Nicole|Nicole]] 07:12, 26 August 2008 (UTC)
::: For physical description used "content type" in the field file upload? --Seesko 07:45, 5 September 2008 (UTC)
 
== Feedback zu Teaching (Lecture/Courseware) ==
 
easy submisssion:
add subject, abstract, event title, event place
:: I don't understand, why you need event title and place. Are the options for title and number of courseware (like in eDoc) not adequate? --Seesko 07:49, 5 September 2008 (UTC)
 
full submission:
add event title, event place
 
:: Added data. --[[User:Nicole|Nicole]] 07:26, 26 August 2008 (UTC)
 
also this should really be another metadata scheme.
:: What is meant by should be another metadata scheme? --[[User:Nicole|Nicole]] 07:26, 26 August 2008 (UTC)
 
''comments by Karin''
 
=== eDoc to PubMan mapping issues ===
 
* shall we add sequencenumber, start- and enddate of event, publisher, publisheraddress and table of contents? They can be specified via eDoc and would otherwise get lost.
 
== Feedback zu Thesis (Hochschulschriften) ==
 
general remark:
the way Phd thesis or other thesis are approved and publ. differ from country to country.
 
A date of approval could be matched to date accepted rather than date created.
 
easy submission:
add date publ. in print, degree type, subject, keyword
 
full submission:
add: all dates (user should be able to enter dates), source genre and source title (since PHd thesis
eg. in our institute appear within an institute's series), alternative title, source publisher, source
place, source volume
(''comments by Karin)''
 
:: Added fields. --[[User:Nicole|Nicole]] 07:48, 26 August 2008 (UTC)
 
easy submission:
add Abstract
(''comment by Elke, 26.08.08'')
 
=== eDoc to PubMan mapping issues ===
* shall we add table of contents? Can be specified via eDoc and this info would otherwise get los.
 
== Feedback zum  Working Paper ==
 
=== eDoc to PubMan migration issues ===
* Add source.issue, publisher, place of publication, review type, source.creators (creators of series), source.title (title of series), source.volume and table of contents, as they can be specified via eDoc and otherwise the information would get lost?
 
== Feedback zum  Report ==
esay submission:
add file, file locator, subject, and keyword
 
full submission
add date created, date modified
''(comments by Karin)''
 
:: added fields --[[User:Nicole|Nicole]] 13:05, 29 August 2008 (UTC)
 
===  eDoc to PubMan Mapping issues ===
* maybe add: start-, enddate of event, name of event (e.g. Experiment), place of event, source creators (creators of the series), table of contents, as they can be specified via eDoc  and otherwise the information will get lost
 
== Feedback zum  Journal ==
 
=== eDoc to PubMan mapping issues ===
* maybe add abstract, discipline and keywords as they can be specified in eDoc and otherwise this information would get lost in PubMan.
 
== Feedback zum Issue ==
 
easy submission:
genre, title of issue, creator(s), keyword, abstract, source genre, source title,
date within a pull down menu
(we as moderators should be able to identify the issue and thus need this info)
 
full submisssion
add creators, all dates (created...-> published)
total number of pages, language of publication, keyword, abstract, alternative title,
start page, end page, invited
(comments by Karin)
:: Added fields. --[[User:Nicole|Nicole]] 12:12, 29 August 2008 (UTC)
 
=== eDoc to PubMan migration issues ===
* shall we add table of contents? This can be specified via eDoc and otherwise this information would get lost.
 
== Feedback zur  Series ==
full submission:
add date created label it as: starting date of series, identifier
(comments by Karin)
 
:: Will be checked. --[[User:Nicole|Nicole]] 07:46, 29 August 2008 (UTC)
 
=== eDoc to PubMan mapping issues ===
* maybe add abstract and keywords, as they can be specified via eDoc and otherwise this information would get lost in PubMan
 
== Feedback zu  Other ==
'''GUI Feedback:'''
 
* Is this the old 'Edit Item' then with all fields available? If one has already chosen a genre we should not allow to 'show all fields available'.
--[[User:Rkiefl|Rupert]] 08:24, 11 August 2008 (UTC)
:: Other is not the old edit item mask. It is a more generic way of a genre specific entry mask. Users put all publications into other where there is no appropriate genre. It can be though possible, that in a later stage a new genre specific entry mask will be defined and some of the entries, which where entered as "other" will be transfered into that newly created genre. --[[User:Nicole|Nicole]] 11:32, 10 September 2008 (UTC)
 
*To better see all issues, i would propose to have single matrix with all genres for easy submission and for full submission. Would re-think if also easy submission should be genre specific. --[[User:Natasab|Natasa]] 16:09, 19 August 2008 (UTC)
:: Will be done as soon as I have the final feedback from Andrea. --[[User:Nicole|Nicole]] 11:32, 10 September 2008 (UTC)
 
=== eDoc to PubMan mapping issues ===
* add dateofevent, enddateofevent, name of event, place of event, refereed (review type), table of contents? They can be specified via eDoc and otherwise the information would get lost
 
== Outcome Meeting of 20.08.==
Participants: Ulla, Natasa, Michael M., Tobias, Rupert
 
Option A is preferred:
 
*allow change of genre any time during creation or editing of an item
*when changing all meta data which are not allowed in new genre, display a persistent message prominently like: "If the genre is changed you might loose previously entered data, because it is not allowed for the genre you select". The last selected genre type is the reference.
*data which matches between two genres is kept
*define default- and genre specific labels where needed
*in case a genre is changed, switch to genre specific labels if available
*use case "use item as template": the genre of source item is inherited for the new item, ie. edit mask provides respective elements. (use case has to be adapted to refer to final genre-specific matrix)--[[User:Uat|Ulla]] 07:47, 21 August 2008 (UTC)
*use case "create revision": the genre of source item is inherited for the new item, i.e. edit mask provides respective elemetns.(use case has to be adapted to refer to final genre-specific matrix)--[[User:Uat|Ulla]] 07:47, 21 August 2008 (UTC)
*for ingestion: ingest of external items will be based on mapping. mapping will include the genre-specific constraints, ie. it might be, that some of external data is not ingested.--[[User:Uat|Ulla]] 07:47, 21 August 2008 (UTC)
*use case fetch metadata: the mapping has to include the genre-specific constraints, ie it might be, that some of external data is not fetched/stored.--[[User:Uat|Ulla]] 07:48, 21 August 2008 (UTC)
 
 
Option B:
 
*select genre type once together with context
*genre can not be changed afterwards (only as special editing operation; similar to change collection)

Latest revision as of 12:01, 1 April 2010

Actually why not linking this table to Publication Types VES ( http://colab.mpdl.mpg.de/mediawiki/ESciDoc_PublicationTypes_VES )? We are doing double work - and it always has to be specified on two places, whenever there is a change :) --Natasa 12:01, 1 April 2010 (UTC)

Vocabulary Encoding Schemes

Coordinated Universal Time

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=Talk:PubMan_Func_Spec_Genre_specific_Submission&oldid=50452"