Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Citation format #178

Open
mkrzmr opened this issue Feb 21, 2024 · 4 comments
Open

Citation format #178

mkrzmr opened this issue Feb 21, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@mkrzmr
Copy link

mkrzmr commented Feb 21, 2024

strong CLARIN requirement!!!:
Current >
Cite as: Linguistically annotated multilingual comparable corpora of parliamentary debates in English ParlaMint-en.ana 3.0. Retrieved Nov 20, 2023 from https://marketplace.sshopencloud.eu/dataset/IYPYqo

Change to what is provided by CLARIN:

Erjavec, Tomaž; et al., 2023, Multilingual comparable corpora of parliamentary debates ParlaMint 3.0, Slovenian language resource repository CLARIN.SI, ISSN 2820-4042, http://hdl.handle.net/11356/1486.

Probably different citations formats:

Datasets, Publications (refer to source repository)
Workflows (original material, refer to the MP)
Tool/Service
Url: most prominent: so fine with accessibleaT
Two citation fields? Cite this MP page/Cite the source
Template: actors (order? role?) + date + label + original source + externalIDs
Which citation style to use?

@mkrzmr mkrzmr self-assigned this Feb 21, 2024
@mkrzmr
Copy link
Author

mkrzmr commented Feb 21, 2024

APA

Lastname, F. M. (Year, Month Date). Title of page. Repo name. URI. URL

@KlausIllmayer
Copy link

Just keep in mind that we use the same citation format for all items of the marketplace. For tools the actors to cite are not always easy to identify, see e.g. https://marketplace.sshopencloud.eu/tool-or-service/87wJWo - who is the person/organisation to cite? I guess it can be only handled by the role, so you would also need to define which role must an actor have, so that this actor is part of the citation. But I see, you mention that we may need different citation formats for the different categories.

In the mentioned example CLARIN does not provide all relevant information. There is no information about "Erjavec, Tomaž; et al." in the dataset that is ingested (see https://github.com/clarin-eric/resource-families-html-generator/blob/master/rfhg/static/resource_families/Corpora/Parliamentary%20corpora/1-Parliamentary%20corpora%20in%20the%20CLARIN%20infrastructure.csv line 2). They should add such a field in their source, otherwise we can't add this information to the citation. The same is true for the title, if they like to have a different title, they need to change their source. We can only do this based on the data we get.

Something to discuss is the URL: we once decided that the "cite as" acts as a helper function so that people can copy&paste this to refer to our - SSH Open Marketplace - site. From there you may get a persistent identifier like the handle.net-id directly on the page but not as part of the "cite as". I'm not sure if it makes sense to really have a meta-citation here, that directly links to the referenced item, for me this sounds more like something a repository should do but not the SSHOMP.

@mkrzmr mkrzmr added the enhancement New feature or request label Mar 12, 2024
@laureD19
Copy link
Contributor

discussing it with @kreetrapper - the idea would be to shut the "cite as" down in the frontend as long as we don't have a proper ingest for the Clarin resource families (new and clean ingest will happen this year from which we would be able to reconstruct a proper citation).
I'm creating another issue with high priority to "kill" the cite as in the interface in the meantime.

@laureD19
Copy link
Contributor

laureD19 commented Jun 6, 2024

dependencies with https://github.com/SSHOC/SSHOMP-Ingest/issues/44 -
on hold until we have new CLARIN Resource Families data in the MP - although we could already decide on the format/template to be implemented for each item type based on existing MP metadata fields

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants